linux-kernel - Re: [RFC/PATCH] - revert generic_fillattr stat->blksize to PAGE_CACHE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <op.tjzjdji6q8etvz@linbox.localdomain>
Date:	Sun, 03 Dec 2006 14:21:09 +0100
From:	col-pepper@...king.net
To:	linux-kernel@...r.kernel.org
Subject: Re: [RFC/PATCH] - revert generic_fillattr stat->blksize to PAGE_CACHE_SIZE

I am using a 2.6.18.2 based kernel and see lots of broken fs due to this  
"diet". eg cloop

I hope some general lessons can be drawn about the necessity and  
desirablility of such changes that (predictably) invoke broadband breakage.

This kind of change and the breakage and dependancy issues they create are  
what makes linux a nightmare to maintain.

While it seems some improvement and clean up may result from this getting  
attention, it appears that the inode structure is back to it's original  
size. Which is quite probably the way it should have stayed all along.

Hopefully this has now stablised.

What kernel release contains code where all this calms down and I dont  
need to search patches and updates for modules in order to get basics to  
work again?

Alternatively can I simply revert the original diet patch on my 2.6.18.2  
to maintain working fs modules?

Thanks for your replys.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/