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, 12 May 2009 10:17:19 +0530 From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> To: Theodore Tso <tytso@....edu> Cc: cmm@...ibm.com, sandeen@...hat.com, linux-ext4@...r.kernel.org Subject: Re: [PATCH 1/3] ext4: Properly initialize the buffer_head state On Mon, May 11, 2009 at 11:17:56PM -0400, Theodore Tso wrote: > On Thu, May 07, 2009 at 04:09:28PM +0530, Aneesh Kumar K.V wrote: > > These buffer_heads are allocated on stack and are > > used only to make get_blocks calls. So we can set the > > b_state to 0 > > > > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com> > > I've rewritten the commit description to this: > > ext4: Properly initialize the buffer_head state > > From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> > > These struct buffer_heads are allocated on the stack (and hence are > initialized with stack garbage). They are only used to call a > get_blocks() function, so that's mostly OK, but b_state must be > initialized to be 0. > > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com> > Signed-off-by: "Theodore Ts'o" <tytso@....edu> > > Comments? > good. -aneesh -- 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