From: "Kay Sievers" <kay.sievers@vrfy.org>
To: Greg KH <gregkh@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Tilman Schmidt <tilman@imap.cc>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
Hugh Dickins <hugh@veritas.com>
Subject: Re: 2.6.21-rc7-mm2 crash: Eeek! page_mapcount(page) went negative! (-1)
Date: Wed, 2 May 2007 14:14:11 +0200 [thread overview]
Message-ID: <3ae72650705020514m1e36caadtc9d64b5439b0cd03@mail.gmail.com> (raw)
In-Reply-To: <20070502074305.GA7761@suse.de>
On 5/2/07, Greg KH <gregkh@suse.de> wrote:
> On Wed, May 02, 2007 at 12:10:00AM -0700, Andrew Morton wrote:
> > On Wed, 02 May 2007 09:01:22 +0200 Tilman Schmidt <tilman@imap.cc> wrote:
> >
> > > Am 30.04.2007 21:46 schrieb Andrew Morton:
> > > > Not really - everything's tangled up. A bisection search on the
> > > > 2.6.21-rc7-mm2 driver tree would be the best bet.
> > >
> > > And the winner is:
> > >
> > > gregkh-driver-driver-core-make-uevent-environment-available-in-uevent-file.patch
> > >
> > > Reverting only that from 2.6.21-rc7-mm2 gives me a working kernel
> > > again.
> >
> > cripes.
> >
> > +static ssize_t show_uevent(struct device *dev, struct device_attribute *attr,
> > + char *buf)
> > +{
> > + struct kobject *top_kobj;
> > + struct kset *kset;
> > + char *envp[32];
> > + char data[PAGE_SIZE];
> >
> > That won't work too well with 4k stacks.
Yeah, sorry.
> Wait, even though this isn't good, it shouldn't have been hit by anyone,
> that file used to not be readable, so I doubt userspace would have been
> trying to read it...
>
> Tilman, what version of HAL and udev do you have on your machine?
>
> Kay, did you get the 'read the uevent file' code already into udev
> and/or HAL?
Only udevtest uses this at the moment, but that is only used for debugging.
It's probably the brain-dead libsysfs, which opens and reads every
file in /sys, even when nobody is interested in the data.
Thanks,
Kay
--
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>
next prev parent reply other threads:[~2007-05-02 12:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070425225716.8e9b28ca.akpm@linux-foundation.org>
[not found] ` <46338AEB.2070109@imap.cc>
2007-04-28 21:10 ` Andrew Morton
2007-04-28 22:06 ` Hugh Dickins
2007-04-30 17:17 ` Tilman Schmidt
2007-04-30 18:21 ` Andrew Morton
2007-04-30 19:28 ` Tilman Schmidt
2007-04-30 19:46 ` Andrew Morton
2007-04-30 21:32 ` Tilman Schmidt
2007-05-01 11:26 ` Tilman Schmidt
2007-05-02 3:10 ` Greg KH
2007-05-02 7:01 ` Tilman Schmidt
2007-05-02 7:02 ` Greg KH
2007-05-02 7:10 ` Andrew Morton
2007-05-02 7:28 ` Greg KH
2007-05-02 7:43 ` Greg KH
2007-05-02 9:41 ` Tilman Schmidt
2007-05-02 22:06 ` Greg KH
2007-05-02 12:14 ` Kay Sievers [this message]
2007-05-02 7:52 ` Greg KH
2007-05-02 17:36 ` Tilman Schmidt
2007-05-02 20:07 ` Andrew Morton
2007-05-02 21:22 ` Tilman Schmidt
2007-05-02 7:10 ` Nick Piggin
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=3ae72650705020514m1e36caadtc9d64b5439b0cd03@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=tilman@imap.cc \
/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