From: Dave Jones <davej@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Michael Buesch <mb@bu3sch.de>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: NULL pointer dereference in sysfs_readdir
Date: Sun, 22 Oct 2006 14:11:02 -0400 [thread overview]
Message-ID: <20061022181102.GC27152@redhat.com> (raw)
In-Reply-To: <453B352A.5050700@s5r6.in-berlin.de>
On Sun, Oct 22, 2006 at 11:08:58AM +0200, Stefan Richter wrote:
> What if "next" became NULL afterwards? I know it's unlikely (but so is
> the whole bug, given that we have just one reporter despite the bug's
> age), but is it impossible? IOW does sysfs_readdir have any indirect
> mutex protection?
>
> Dave, do you patch sysfs datatypes in FC's kernel, or types they include?
Not that I recall. <linux/sysfs.h> is untouched in the trees I just
looked at (only have .18 ones handy right now)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-10-22 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 8:43 NULL pointer dereference in sysfs_readdir Stefan Richter
2006-10-21 20:04 ` Michael Buesch
2006-10-21 21:09 ` Stefan Richter
2006-10-21 21:25 ` Michael Buesch
2006-10-22 9:08 ` Stefan Richter
2006-10-22 10:40 ` Michael Buesch
2006-10-22 18:11 ` Dave Jones [this message]
2006-10-30 12:36 ` Maneesh Soni
2006-10-31 8:36 ` Stefan Richter
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=20061022181102.GC27152@redhat.com \
--to=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=stefanr@s5r6.in-berlin.de \
/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