linux-kernel - Re: linux-next: Tree for December 14 (New tree: vfs-scale)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 15 Dec 2010 17:02:53 +1100
From:	Nick Piggin <npiggin@...nel.dk>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	sedat.dilek@...il.com, Sedat Dilek <sedat.dilek@...glemail.com>,
	Nick Piggin <npiggin@...nel.dk>,
	Nick Kossifidis <mickflemm@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Peter Hutterer <peter.hutterer@...-t.net>
Subject: Re: linux-next: Tree for December 14 (New tree: vfs-scale)

On Tue, Dec 14, 2010 at 10:33:39PM +1100, Stephen Rothwell wrote:
> Hi Sedat,
> 
> On Tue, 14 Dec 2010 10:38:35 +0100 Sedat Dilek <sedat.dilek@...glemail.com> wrote:
> > I played yesterday with the new refreshed patchset (manually merged
> > and fixed) against systemd-v15 with kgdb/kdb.
> > Oh yes, there is a "dmesg" command :-) and with "btp $pid" I yesterday
> > night saw a NULL dereference in the backtrace.
> > Currently, I am compiling linux-next (next-20101214) and will take
> > some pictures with my digicam.

Thanks for testing, I would be very interested to know if your bug
has gone away or not, we never quite got to the bottom of that. BTW.
capturing the top of the oops is important, if possible. If you don't
have a serial console or anything to capture it, could you try
increasing the resolution of your console so it fits more in?

> > Some recommends (not that I want to teach you as GIT is for me new
> > playground and I follow mostly the commit-messages, which not means I
> > understand the complexity of the patchset), but ...
> > 
> > 1. Please give commits a proper/sane "commit subject"
> > "Build fix" or "Fixed build failure" is not saying much.

Yes, that will be folded in properly before upstream merge.

> > 2. Add credits for people investing time to test and report
> > Same commits did not have also credits for people reporting the build failures.
> > A reference to LKML posting would be fine in the "commit-body" (sorry
> > for my comparison with Email, do not know the GIT term).
> > 
> > This all is not to punish you, it is for following and documenting the
> > whole process.
> > 
> > Peter Hutterer has a wonderful blog article "On commit messages"
> > concerning this topic.
> > If all of us would follow them, the working-together will be more fruitful.

That is a good point, and if I don't give testers enough credit, I'm
sorry because they're a vital part of the chain. Probably because I
have too many bugs that it would clutter my changelogs to credit
everyone who finds one :)

I definitely like to credit testers and reporters in bugfix patches to
upstream kernel, but I find that when they're testing a development
kernel, then the bugfix patches get merged back into the patch that
introduces the bug before being merged.

It wouldn't hurt to keep references to these problems though, not only
to acknoledge the testers, but also as a reference to potential pitfalls
or problematic areas in the commit.

So, I'll try to take your suggestion on board.

Thanks,
Nick

--
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/