mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jessica Yu <jeyu@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Aaron Tomlin <atomlin@redhat.com>,
	linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: module: When modifying a module's text ignore modules which are going away too
Date: Wed, 23 Nov 2016 10:33:44 -0800	[thread overview]
Message-ID: <20161123183344.ltp6w3wps4feei7g@jeyu> (raw)
In-Reply-To: <20161123110049.1c458298@gandalf.local.home>

+++ Steven Rostedt [23/11/16 11:00 -0500]:
>On Wed, 9 Nov 2016 05:40:58 -0500
>Jessica Yu <jeyu@redhat.com> wrote:
>
>> +++ Aaron Tomlin [07/11/16 11:46 +0000]:
>> >Hi Jessica,
>> >
>> >Any thoughts?
>>
>> Hi Aaron,
>>
>> Thanks for your patience as I slowly work through a large swath of emails :-)
>>
>> Anyway, this looks fine to me. A going module's text should be (or
>> soon will be) rw anyway, so checking for going modules in the ro
>> case should be enough.
>>
>> Rusty, if you give your ack for the second patch, I can apply both
>> patches to my modules-next branch. I'll also incorporate Steven's
>> suggestion for a comment explaining why going modules shouldn't be
>> converted to ro in this context.
>>
>
>Hi Jessica,
>
>Have you pulled these in? I haven't noticed them in linux-next.

I currently have this queued up for 4.10. I'm still clearing up some
(unrelated to this patch) maintainership transition questions, but
expect the new modules tree to be pushed out and included in -next
by this week.

Thanks,
Jessica

  reply	other threads:[~2016-11-23 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 16:18 [RFC PATCH 0/2] Possible race between load_module() error handling and kprobe registration ? Aaron Tomlin
2016-10-20 16:18 ` [RFC PATCH 1/2] module: Ensure a module's state is set accordingly during module coming cleanup code Aaron Tomlin
2016-10-26  0:54   ` Rusty Russell
2016-11-09 10:12     ` Jessica Yu
2016-11-16 15:49       ` Miroslav Benes
2016-11-23 23:41         ` Jessica Yu
2016-10-20 16:18 ` [RFC PATCH 2/2] module: When modifying a module's text ignore modules which are going away too Aaron Tomlin
2016-10-26  1:05   ` Rusty Russell
2016-10-26 12:09     ` Steven Rostedt
2016-10-27  9:36       ` [RFC PATCH v2 " Aaron Tomlin
2016-10-27 13:49         ` Steven Rostedt
2016-11-07 11:46           ` Aaron Tomlin
2016-11-09 10:40             ` Jessica Yu
2016-11-23 16:00               ` Steven Rostedt
2016-11-23 18:33                 ` Jessica Yu [this message]
2016-11-18  6:15         ` [RFC PATCH v2 2/2] " Rusty Russell

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=20161123183344.ltp6w3wps4feei7g@jeyu \
    --to=jeyu@redhat.com \
    --cc=atomlin@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.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
all inboxes | Powered by JetHome®