| 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: Thu, 19 Oct 2006 16:09:00 -0700 From: Mark Fasheh <mark.fasheh@...cle.com> To: Nick Piggin <npiggin@...e.de> Cc: linux-kernel@...r.kernel.org, nickpiggin@...oo.com.au, akpm@...l.org Subject: Re: + fs-prepare_write-fixes.patch added to -mm tree On Thu, Oct 19, 2006 at 07:25:37AM +0200, Nick Piggin wrote: > I sent an RFC to linux-fsdevel, did you get that? Yeah, I don't think I thought of my concerns at the time. > I was planning to cc some maintainers, including you, for those > filesystems that are non-trivial. I just hadn't had a chance to > test it properly last night. Cool, I appreciate that. > OK thanks for looking at that. If the length of the commit is greater > than 0 (but still short), then the page is uptodate so it should be > fine to commit what we have written, I think? That seems to make sense to me. > If the length is zero, then we probably want to roll back entirely. The thing is, rollback might be hard (or expensive) for some file systems with more complicated tree implementations, etc. Do we have the option in this case of just zeroing the newly allocated portions and writing them out? Userspace would then just be seeing that like any other hole. --Mark -- Mark Fasheh Senior Software Developer, Oracle mark.fasheh@...cle.com - 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