From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] stack tracing causes: kernel/module.c:271 module_assert_mutex_or_preempt
Date: Wed, 5 Apr 2017 21:07:02 -0700 [thread overview]
Message-ID: <20170406040702.GW1600@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170405213145.53332c62@grimm.local.home>
On Wed, Apr 05, 2017 at 09:31:45PM -0400, Steven Rostedt wrote:
> On Wed, 5 Apr 2017 13:42:29 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > > OK, do you want me to send you a patch, or should I take your patch
> > > into my tree and add this?
> >
> > Given that I don't seem to have disable_stack_tracer() and
> > enable_stack_tracer(), could you please add them in?
>
> That's what I meant about "send you a patch" :-)
Reading/comprehension-challenged today, aren't I?
This doesn't conflict with anything in my tree, so either your tree
or my tree is fine by me. The advantage of your tree is that you
could easily sync it up with the other changes needed.
Thanx, Paul
next prev parent reply other threads:[~2017-04-06 4:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 13:32 [BUG] stack tracing causes: kernel/module.c:271 module_assert_mutex_or_preempt Steven Rostedt
2017-04-05 16:25 ` Paul E. McKenney
2017-04-05 16:45 ` Steven Rostedt
2017-04-05 17:59 ` Paul E. McKenney
2017-04-05 18:54 ` Steven Rostedt
2017-04-05 19:08 ` Paul E. McKenney
2017-04-05 19:21 ` Steven Rostedt
2017-04-05 19:39 ` Paul E. McKenney
2017-04-05 19:52 ` Steven Rostedt
2017-04-05 20:42 ` Paul E. McKenney
2017-04-06 1:31 ` Steven Rostedt
2017-04-06 4:07 ` Paul E. McKenney [this message]
2017-04-06 2:12 ` Steven Rostedt
2017-04-06 4:15 ` Paul E. McKenney
2017-04-06 14:14 ` Steven Rostedt
2017-04-06 14:59 ` Paul E. McKenney
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=20170406040702.GW1600@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).