From: "Bret Towe" <magnade@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc1 bttv modprobe null pointer dereference
Date: Fri, 7 Jul 2006 10:02:47 -0700 [thread overview]
Message-ID: <dda83e780607071002ibfe2514g720fa4bec092f8ed@mail.gmail.com> (raw)
In-Reply-To: <20060706233521.686300d2.akpm@osdl.org>
On 7/6/06, Andrew Morton <akpm@osdl.org> wrote:
> On Thu, 6 Jul 2006 22:19:09 -0700
> "Bret Towe" <magnade@gmail.com> wrote:
>
> > > > Code: 4c 8b bf 48 01 00 00 48 8b bf c0 00 00 00 8b 5e 10 48 81 c7
> > > > RIP [<ffffffff802f1f9b>] sysfs_add_file+0x2b/0xb0
> > > > RSP <ffff81002ac71c28>
> > > > CR2: 0000000000000149
> > >
> > > There don't seem to have been significant changes in bttv-driver.c for some
> > > time, and we're seeing a few reports like this. I'm suspecting that either
> > > a sysfs/driver-core change was wrong, or previously wrong driver behaviour
> > > is now causing oopses.
> > >
> > > And Mauro is offline until July 12.
> > >
> > > Can you send the .config please?
> >
> > of course
>
> I spent ten minutes and got lost. I suspect videodev's class_device
> handling is wrong, but I fail to spot it.
>
> This might tell us something.
i dont see any new error messages in dmesg
looking at the trace it looks like its dieing before it gets to where this
patch would be used?
next prev parent reply other threads:[~2006-07-07 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 3:51 Bret Towe
2006-07-07 4:52 ` Andrew Morton
2006-07-07 5:19 ` Bret Towe
2006-07-07 6:35 ` Andrew Morton
2006-07-07 17:02 ` Bret Towe [this message]
2006-07-07 6:46 ` Dave Jones
2006-07-07 17:04 ` Bret Towe
2006-07-07 22:27 ` Bret Towe
2006-07-07 5:37 ` Bret Towe
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=dda83e780607071002ibfe2514g720fa4bec092f8ed@mail.gmail.com \
--to=magnade@gmail.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®