From: Steven Rostedt <rostedt@goodmis.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>, Dave Hansen <dave@sr71.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-next <linux-next@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Kristen Carlson Accardi <kristen@linux.intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Rik van Riel <riel@redhat.com>, Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline
Date: Sat, 7 Feb 2015 10:20:02 -0500 [thread overview]
Message-ID: <20150207102002.4edc054c@grimm.local.home> (raw)
In-Reply-To: <CA+icZUX6diUTU0N3=PF1XkiwJokUKxWdAczbGjK4epv+FxpVcg@mail.gmail.com>
On Sat, 7 Feb 2015 09:01:34 +0100
Sedat Dilek <sedat.dilek@gmail.com> wrote:
> - Tested-by's
> - Reference of 2/2 to 1/2
The two are together in the series and fix two different bugs. They do
not need to reference each other.
> - 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)
The first patch fixes a bug introduced in 3.18. There would be no splat
in 3.17 because the check didn't exist then. But the RCU reference
while cpu offline (second bug) was introduced in 3.17 and that is what
the second patch fixes.
>
> 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)?
We don't need more tags.
> 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
>
I may add that, but more appropriate would be to add the commit that
fixes the bug to the bug report.
> Maybe ask godfather of SubmittingPatches greg-kh?
>
Heh, I haven't read that document in years.
-- Steve
next prev parent reply other threads:[~2015-02-07 15:20 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 20:06 [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU Steven Rostedt
2015-02-06 20:06 ` [PATCH 1/2] tracing: Add condition check to RCU lockdep checks Steven Rostedt
2015-02-06 20:11 ` Steven Rostedt
2015-02-06 20:13 ` [PATCH 1/2 v2] " Steven Rostedt
2015-02-06 20:06 ` [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline Steven Rostedt
2015-02-06 23:27 ` Paul E. McKenney
2015-02-07 4:02 ` Steven Rostedt
2015-02-07 8:01 ` Sedat Dilek
2015-02-07 15:20 ` Steven Rostedt [this message]
2015-02-07 19:50 ` Sedat Dilek
2015-02-07 20:09 ` Paul E. McKenney
2015-02-07 20:14 ` Sedat Dilek
2015-02-07 21:52 ` Steven Rostedt
2015-02-07 22:14 ` Paul E. McKenney
2015-02-07 23:01 ` Sedat Dilek
2015-02-07 23:48 ` Dave Hansen
2015-02-07 8:13 ` Sedat Dilek
2015-02-07 15:22 ` Steven Rostedt
2015-02-06 21:07 ` [PATCH 0/2] tracing/tlb/x85: Fix splat of calling RCU trace code on offline CPU Sedat Dilek
2015-02-06 21:18 ` Steven Rostedt
2015-02-06 21:19 ` Steven Rostedt
2015-02-06 21:23 ` Sedat Dilek
2015-02-06 21:27 ` Steven Rostedt
2015-02-06 21:24 ` Steven Rostedt
2015-02-06 21:29 ` Sedat Dilek
2015-02-06 21:21 ` Sedat Dilek
2015-02-06 21:28 ` Steven Rostedt
2015-02-06 21:33 ` Steven Rostedt
2015-02-06 21:38 ` Paul E. McKenney
2015-02-06 22:13 ` Sedat Dilek
2015-02-06 22:35 ` Steven Rostedt
2015-02-06 22:48 ` Paul E. McKenney
2015-02-06 22:51 ` Sedat Dilek
2015-02-06 23:02 ` Sedat Dilek
2015-02-06 23:04 ` Paul E. McKenney
2015-02-06 23:04 ` Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2015-02-06 20:11 [PATCH 2/2] x86/tbl/trace: Do not trace on CPU that is offline Sedat Dilek
2015-02-06 20:21 ` Steven Rostedt
2015-02-06 20:23 ` Sedat Dilek
2015-02-06 20:26 ` Steven Rostedt
2015-02-06 21:34 ` Steven Rostedt
2015-02-06 21:39 ` Sedat Dilek
2015-02-06 21:42 ` Steven Rostedt
2015-02-06 22:32 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150207102002.4edc054c@grimm.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=hpa@linux.intel.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox