linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Tejun Heo <tj@kernel.org>, Martin KaFai Lau <kafai@fb.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Christoph Lameter <cl@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC NEXT] mm: Fix suspicious RCU usage at kernel/sched/core.c:7318
Date: Tue, 16 Jun 2015 01:02:09 -0500	[thread overview]
Message-ID: <557FBBE1.2060301@lwfinger.net> (raw)
In-Reply-To: <20150616053702.GA29055@linux.vnet.ibm.com>

On 06/16/2015 12:37 AM, Kamalesh Babulal wrote:
> * Larry Finger <Larry.Finger@lwfinger.net> [2015-06-15 16:25:18]:
>
>> Beginning at commit d52d399, the following INFO splat is logged:
>>
>
> [...]
>
>> ---
>>   include/linux/kmemleak.h |  3 ++-
>>   mm/kmemleak.c            |  9 +++++----
>>   mm/kmemleak.c.rej        | 19 +++++++++++++++++++
>>   mm/percpu.c              |  2 +-
>>   4 files changed, 27 insertions(+), 6 deletions(-)
>>   create mode 100644 mm/kmemleak.c.rej
>
> Patch creates kmemleak.c.rej file.

Sorry about that. This one was an RFC. I'll fix that before the final submission.

Larry


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-06-16  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 21:25 Larry Finger
2015-06-16  5:37 ` Kamalesh Babulal
2015-06-16  6:02   ` Larry Finger [this message]
2015-06-16  8:44 ` Catalin Marinas
2015-06-16  8:48   ` Catalin Marinas
2015-06-16 21:07 ` Martin KaFai Lau
2015-06-17  2:43   ` Larry Finger
2015-06-17  4:15     ` Martin KaFai Lau

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=557FBBE1.2060301@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=catalin.marinas@arm.com \
    --cc=cl@linux-foundation.org \
    --cc=kafai@fb.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tj@kernel.org \
    /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