From: Chris Rankin <rankincj@yahoo.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux 2.6.20.1 - unable to handle kernel paging request - accessing freed memory?
Date: Tue, 27 Feb 2007 17:04:12 +0000 (GMT) [thread overview]
Message-ID: <714641.9150.qm@web52907.mail.yahoo.com> (raw)
In-Reply-To: <84144f020702270642q4e371175y2a6c922e030e1f3b@mail.gmail.com>
--- Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > Call Trace:
> > [<c01839fe>] sysfs_release+0x2d/0x4c
> > [<c015124b>] __fput+0x96/0x13c
>
> So udevd is closing a sysfs attribute file but the pointer passed to
> module_put is bogus. Looks like the sysfs dentry was already taken
> down by release_sysfs_dirent(). Can you reproduce this at will? Does
> the oops happen in older kernels?
No, unfortunately I can't. Last night was the first time this ever happened (while I was starting
up World of Warcraft/Wine), so I have no idea which sysfs attribute it is talking about here.
Cheers,
Chris
___________________________________________________________
Inbox full of unwanted email? Get leading protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html
prev parent reply other threads:[~2007-02-27 17:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 1:26 [BUG] Linux 2.6.20.1 - unable to handle kernel paging request - accessing freed memory? Chris Rankin
2007-02-26 18:42 ` Randy Dunlap
2007-02-26 19:57 ` [Alsa-devel] " Takashi Iwai
2007-02-27 13:25 ` Chris Rankin
2007-02-27 14:48 ` Pekka Enberg
2007-03-01 11:28 ` Chris Rankin
2007-03-01 11:32 ` Pekka J Enberg
2007-03-01 13:22 ` Chris Rankin
2007-03-01 13:27 ` Chris Rankin
2007-03-07 23:29 ` Chris Rankin
2007-03-08 1:26 ` Chris Rankin
2007-02-26 20:08 ` Chris Rankin
2007-02-27 14:42 ` Pekka Enberg
2007-02-27 17:04 ` Chris Rankin [this message]
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=714641.9150.qm@web52907.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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