| 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: <20101110163224.GB15130@infradead.org> Date: Wed, 10 Nov 2010 11:32:25 -0500 From: Christoph Hellwig <hch@...radead.org> To: Nick Piggin <npiggin@...nel.dk> Cc: Christoph Hellwig <hch@...radead.org>, Al Viro <viro@...IV.linux.org.uk>, Linus Torvalds <torvalds@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [patch 4/6] fs: d_delete change On Wed, Nov 10, 2010 at 09:08:33AM +1100, Nick Piggin wrote: > On Tue, Nov 09, 2010 at 11:25:16AM -0500, Christoph Hellwig wrote: > > The patch looks fine to me, and I'm also fine with merging it ASAP. > > But the patch subject and commit message are not very descriptive. > > How is the commit message not descriptive? The first sentence > summarises exactly what the change does. The last says why it > is required. In the middle are some details. foo change is about as useless as a subject could be. "fs: idempotent d_delete" from your old tree was much better. As far as the commit message is concerned I think the most important bit is that we do not call it from prune_one_dentry anymore, which is the things that might matter to any complex filesystem maintainer looking at the changelog. The other things I didn't like was the introductionary blurb, but from reading the answer to the previous comment is seems like that wsn't intentional anyway. -- 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