home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.kernel      Debian kernel discussions      2,884 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,576 of 2,884   
   Ben Hutchings to All   
   Bug#1126710: linux-image-6.18.5+deb14-am   
   04 Feb 26 18:20:01   
   
   XPost: linux.debian.bugs.dist   
   From: ben@decadent.org.uk   
      
   On Sat, 2026-01-31 at 12:26 +0100, 10dmar10 wrote:   
   > Am 31.01.26 um 11:02 schrieb Salvatore Bonaccorso:   
   >  > Hi,   
   >  >   
   >  > On Sat, Jan 31, 2026 at 10:08:25AM +0100, 10dmar10 wrote:   
   [...]   
   >  >> while no longer used by default, XFS V4 support is still useful for   
   accessing   
   >  >> legacy XFS V4 file systems as long as kernel supports it.   
   >  >   
   >  > This is correct, the default was changed in upstream with f69260511c69   
   >  > ("xfs: disable deprecated features by default in Kconfig") and I   
   >  > believe we should follow that within the forky release cycle.   
   >  >   
   >  > Thus for forky I do not think we should diverge here from the default   
   >  > and re-enable deprecated features, but probably we should document it   
   >  > at least in the release notes so that people upgrading from trixie to   
   >  > forky are awaere that V4 filesystems will not be supported anymore.   
   >  >   
   >  > A NEWS entry in the packaging itself might be a good idea as well.   
   >  >   
   >  > Regards,   
   >  > Salvatore   
   >    
   > Hi,   
   >    
   > I wrote this bug report because I assumed the release interval for forky as   
   2027    
   > -2030, which is within the kernel removal date for XFS V4 feature in 2030.   
      
   Debian stable releases are supported for 5 years on the most popular   
   architectures.  So for forky this should be 2027-2032.   
      
   > Enabling CONFIG_XFS_SUPPORT_V4 would allow to continue running otherwise    
   > perfectly fine existing legacy XFS V4 filesystems without unnecessary   
   breaking    
   > anything within forky's release cycle...   
      
   Those filesystems must be quite old at this point, since v5 appears to   
   have been the default for new filesystems since xfsprogs 3.2.3 and   
   Debian 9 "stretch".  And they do need to be upgraded at some point due   
   to the upstream EOL (and later, Y2038).  How much would we gain by   
   putting it off another 2 years?   
      
   I agree with Salvatore that this just needs to be documented.   
      
   Ben.   
      
   --    
   Ben Hutchings   
   A free society is one where it is safe to be unpopular.   
                                                         - Adlai Stevenson   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAmmDfYwACgkQ57/I7JWG   
   EQk5yQ//ZUnHDc78tmubE/TCAtuudwmWxtwmO9OHCbIBcxrr6K4cFcHb2ajPLo8o   
   7Aedu0zqb7wLPSz89rJrUTP0kwzPlK2eA0yL3wB/IKe6O6YN517mc046uYNBIN/n   
   sK4Oj95iV8NtsywMkC4VTQbrqp3lGOQy390v+Egm9tsjXFeOAQ6v353qTQqfkQRh   
   +EMekWUsDH2vuQVcR6R1VyP/nRi0/cZ/fexmPLjRiR5XKXm+bgZcNyd6TNXkBD2e   
   k26d/hd3uMMZeAbRRVWozhbfXXIcx1mU4BYpyFxFyAnbANKO6FPB5aQRYDiiE7dE   
   16Rb7HpAvOV15L2ODx8HM9btYGj9gflwEBmMWIk13aIEcIn2DQB4Sn4xhIZoRrDO   
   qKtLrr/0HG0cpclO62/5EhERH1zcC8UJFoKylpC2vUK2UVPRYlxpb1F1OAoRiYo0   
   WCUmCdDx9qBHZGEEnM9xBgQmsqko91KYbajAk8GHlyxYXx+lsa3u5dEnbNlqkxRv   
   KXhlhPg+/7Xz6/BK6HgCHyV0VTWN2NeqRRY95IAoNIxfT3ofLy+Ehh+PLaOygdd7   
   uOENiJkslbexcyZraS7OyRbiTv0wdgLkhmXPX1mUrXOt5VkGTIvjQG0PdVqT3qpS   
   VCPsRqBgOpFr9CHawRLGFhv6wDke35QYnMW5VFkxhN3Sk/Tq3Es=   
   =t6i0   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca