linux-kernel - Re: [tip:core/locking] lockdep, rtmutex, bug: Show taint flags on error

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111206181422.GA11881@elliptictech.com>
Date:	Tue, 6 Dec 2011 13:14:22 -0500
From:	Nick Bowler <nbowler@...iptictech.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Ben Hutchings <ben@...adent.org.uk>, mingo@...hat.com,
	hpa@...or.com, linux-kernel@...r.kernel.org,
	a.p.zijlstra@...llo.nl, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:core/locking] lockdep, rtmutex, bug: Show taint flags on
 error

On 2011-12-06 18:54 +0100, Ingo Molnar wrote:
> * Ben Hutchings <ben@...adent.org.uk> wrote:
> > On Tue, 2011-12-06 at 01:38 -0800, tip-bot for Ben Hutchings wrote:
> > > Commit-ID:  fbdc4b9a6c29befbcca65e5366e5aaf2abb7a013
> > > Gitweb:     http://git.kernel.org/tip/fbdc4b9a6c29befbcca65e5366e5aaf2abb7a013
> > > Author:     Ben Hutchings <ben@...adent.org.uk>
> > > AuthorDate: Fri, 28 Oct 2011 04:36:55 +0100
> > > Committer:  Ingo Molnar <mingo@...e.hu>
> > > CommitDate: Tue, 6 Dec 2011 08:16:49 +0100
> > > 
> > > lockdep, rtmutex, bug: Show taint flags on error
> > > 
> > > Show the taint flags in all lockdep and rtmutex-debug error messages.
> > > 
> > > Signed-off-by: Ben Hutchings <ben@...adent.org.uk>
> > > Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> > > Link: http://lkml.kernel.org/r/1319773015.6759.30.camel@deadeye
> > > Signed-off-by: Ingo Molnar <mingo@...e.hu>
> > [...]
> > 
> > If you disagree with a patch, do not silently drop parts of 
> > it.  I demand that you remove my 'Signed-off-by' as this is 
> > not the change I submitted.
> 
> FYI, there's no "I will only sign off on a patch doing two 
> things if it's applied in full" kind of condition in the SOB 
> definition, allowing that would break the GPL: people have the 
> right to take your modifications to the GPL-ed kernel and modify 
> it further.

If you want to play the GPL card, you will note that the GPL requires
modified versions of a work to carry prominent notices that they have
been modified, including the date of any change.

A signoff by a maintainer does not imply that any modifications have
been made, so I don't think that counts as "prominent".

> Your original patch did two things. Peter did the sensible 
> thing: he split out the print_kernel_ident() changes from your 
> patch which stand on their own and kept your authorship in place 
> - that is what the above patch does.

In which case, the changelog should have been amended to state that
it's a modification of Ben's original submission.

> Once you send it out the SOB is valid and people can (and 
> typically will) modify it - and if you are still the main author 
> (which you are here 100%) then keeping you as the author is the 
> proper approach - Peter added his own SOB after yours.

Linux convention is to add a signoff *and* a description of any changes
to the original submission in square brackets.

Cheers,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.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/