| 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
| ||
|
Message-ID: <29495f1d0705220801v50e53f2dl24f9b198dd31c39c@mail.gmail.com> Date: Tue, 22 May 2007 08:01:26 -0700 From: "Nish Aravamudan" <nish.aravamudan@...il.com> To: "Michael Halcrow" <mhalcrow@...ibm.com> Cc: "Andrew Morton" <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, linux-fsdevel@...r.kernel.org Subject: Re: [PATCH] eCryptfs: Delay writing 0's after llseek until write On 5/22/07, Michael Halcrow <mhalcrow@...ibm.com> wrote: > On Mon, May 21, 2007 at 09:07:08PM -0700, Andrew Morton wrote: > > On Mon, 21 May 2007 18:00:21 -0500 Michael Halcrow <mhalcrow@...ibm.com> wrote: > > > > > Delay writing 0's out in eCryptfs after a seek past the end of the > > > file until data is actually written. > > > > a) why? > > http://www.opengroup.org/onlinepubs/009695399/functions/lseek.html > > ``The lseek() function shall not, by itself, extend the size of a > file.'' > > > b) what is the impact upon a user of them not having this patch? > > Applications that lseek() past the end of the file without writing > will experience unexpected behavior. FWIW, I believe Andrew's point was that critical information for Joe Enduser (and Joe Patch-Ho) was lacking in the original changelog. Thanks, Nish - 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