public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
	Kay Sievers <kay.sievers@suse.de>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: oops in uevent_helper [was: mmotm 2010-01-13-12-17 uploaded]
Date: Thu, 11 Feb 2010 21:57:45 +0100	[thread overview]
Message-ID: <20100211205745.GA18202@basil.fritz.box> (raw)
In-Reply-To: <4B730EE3.4080405@gmail.com>

On Wed, Feb 10, 2010 at 08:54:11PM +0100, Jiri Slaby wrote:
> On 01/23/2010 12:52 AM, Andrew Morton wrote:
> > On Sat, 16 Jan 2010 00:38:32 +0100
> > Jiri Slaby <jirislaby@gmail.com> wrote:
> > 
> >> (fixed subject)
> >>
> >> On 01/15/2010 08:33 PM, Jiri Slaby wrote:
> >>> On 01/13/2010 09:17 PM, akpm@linux-foundation.org wrote:
> >>>> The mm-of-the-moment snapshot 2010-01-13-12-17 has been uploaded to
> >>>
> >>> Hi, it crashes on my machine while booting up. It is a regression
> >>> against 2010-01-06-14-34. Doesn't it ring a bell by a chance?
> >>
> >> Well, memcpying to something like this:
> >> char *uevent_helper = CONFIG_UEVENT_HELPER_PATH;
> >> doesn't sound like a good idea :).
> >>
> >> And it's racy with sysctl path anyway.
> >>
> >> Looks like added by:
> >> sysctl-convert-hotplug-helper-string-to-proc_rcu_string.patch
> 
> Ping Andi.

Sorry, busy with other stuff right now. There was at least one
other unsolved problem in this patch series. I'll try to look
at it on the weekend.

Andrew, it's ok for me if you just drop the series for now;
I'll resubmit.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2010-02-11 20:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 20:17 mmotm 2010-01-13-12-17 uploaded akpm
2010-01-13 22:16 ` mmotm 2010-01-13-12-17 - 'make oldconfig' dies Valdis.Kletnieks
2010-01-14 16:07 ` mmotm 2010-01-13-12-17 uploaded (cgroup) Randy Dunlap
2010-01-14 17:20   ` Ben Blum
2010-01-18  2:03     ` Randy Dunlap
2010-01-14 16:18 ` [PATCH -mmotm] tty.h: make function static Randy Dunlap
2010-01-15 19:33 ` mmotm 2010-01-13-12-17 uploaded Jiri Slaby
2010-01-15 23:38   ` oops in uevent_helper [was: mmotm 2010-01-13-12-17 uploaded] Jiri Slaby
2010-01-22 23:52     ` Andrew Morton
2010-02-10 19:54       ` Jiri Slaby
2010-02-11 20:57         ` Andi Kleen [this message]
2010-02-11 22:25           ` Andrew Morton
2010-02-12  2:39             ` Neil Horman
2010-02-12  3:10               ` Andrew Morton
2010-02-12  5:21             ` Andi Kleen
2010-02-12  5:27               ` Andrew Morton
2010-02-12 17:06                 ` Neil Horman
2010-02-14 17:32                   ` Jiri Slaby
2010-02-14 17:54                     ` Neil Horman
2010-02-15 20:12                   ` Paul E. McKenney
2010-02-15 21:42                     ` Neil Horman
2010-02-15 22:16                       ` Paul E. McKenney
2010-02-16  1:37                         ` Neil Horman

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=20100211205745.GA18202@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=kay.sievers@suse.de \
    --cc=linux-kernel@vger.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