| 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: Mon, 23 Jun 2008 20:42:00 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Nick Piggin <nickpiggin@...oo.com.au> cc: Andrew Morton <akpm@...ux-foundation.org>, Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>, 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 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). Of course, that could cause other problems (eg any VM assertions that shared mappings only contain non-anon pages). Linus -- 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/
Powered by blists - more mailing lists