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]
Date:	Sat, 7 Feb 2015 09:01:34 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>, Dave Hansen <dave@...1.net>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	linux-next <linux-next@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Kristen Carlson Accardi <kristen@...ux.intel.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline

On Sat, Feb 7, 2015 at 5:02 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Fri, 6 Feb 2015 15:27:54 -0800
> "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:
>
>> > Reported-by: Sedat Dilek <sedat.dilek@...il.com>
>> > Suggested-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
>> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
>>
>> Acked-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
>
> Both patches survived all my tests, now I just need an ack by from Dave
> and/or Peter, and I'll push it off to Linus.
>

I took both patches from linux-trace.git/ftrace/urgent.

So, both patches were updated and especially 2/2 misses...

- Tested-by's
- Reference of 2/2 to 1/2
- CC: stable v3.17+/v3.18+ ? (1/2 has a hint for backporting in case
of 3.17+ which is BTW EOL, not sure if there are main distros
supporting linux-3.17.y)

BTW, do you happen to know if there is a someting like a
"Requires-tag" or "Precondition-tag" (for example the Fixes-tag is
very helpful)?
AFAICS people place such information into the commit-message.
I have seen "References:" but this is more to point to a
bug-tracking-system (BTS).

EXAMPLE:

commit 63b03e2d2477586440741677ecac45bcf28d7b1
"mutex: Always clear owner field upon mutex_unlock()"

References: https://bugs.freedesktop.org/show_bug.cgi?id=87955

Maybe ask godfather of SubmittingPatches greg-kh?

- Sedat -

[1] http://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/log/?h=ftrace/urgent
--
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