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
| ||
|
Date: Tue, 24 Jun 2008 22:03:56 +0900 From: Hidehiro Kawai <hidehiro.kawai.ez@...achi.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Nick Piggin <nickpiggin@...oo.com.au>, Andrew Morton <akpm@...ux-foundation.org>, sct@...hat.com, adilger@....com, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, jack@...e.cz, sugita <yumiko.sugita.yf@...achi.com>, Satoshi OSHIMA <satoshi.oshima.fk@...achi.com> Subject: Re: [RFC][PATCH] ext3: don't read inode block if the buffer has a write error Hi all, Thank you for precious comments. Linus Torvalds wrote: > > On Tue, 24 Jun 2008, Nick Piggin wrote: > >>What you want to do is not insane, but the way it is currently being >>done is. As I said, just clearing the uptodate bit might blow up your >>kernel pretty quickly from assertions in the vm. It should be going >>through the whole truncate or invalidate page machinery in order to >>do that. > > Fair enough. > > I would not mind, for example, leaving the uptodate bit, but removing it > from the radix tree or something like that (ie turning it into an > anonymous page for a page-cache page, just removing it from the > hash-queues for a buffer_head). If we move page caches with errors to another radix tree instead of just removing, we may be able to do special handlings: rewrite once, or check the page caches and get rid of them from user space, and so on. > Of course, that could cause other problems (eg any VM assertions that > shared mappings only contain non-anon pages). As Jan and Nick stated, this seems to need a great effort, but I think it is worthwhile to do. Thanks, -- Hidehiro Kawai Hitachi, Systems Development Laboratory Linux Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists