From: Andrew Morton <akpm@osdl.org>
To: Masanari Iida <standby24x7@gmail.com>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: oops with USB Storage on 2.6.14
Date: Wed, 2 Nov 2005 17:21:44 +1100 [thread overview]
Message-ID: <20051102172144.757fe643.akpm@osdl.org> (raw)
In-Reply-To: <38bdcd1f0511011856i3780bf55q3013956dc7e06e3e@mail.gmail.com>
Masanari Iida <standby24x7@gmail.com> wrote:
>
> On 11/1/05, Alan Stern <stern@rowland.harvard.edu> wrote:
> > On Sun, 30 Oct 2005, Andrew Morton wrote:
> >
> > > Masanari Iida <standby24x7@gmail.com> wrote:
> >
> > > > Hello Andrew,
> > > >
> > > > I did disabled CONFIG_DEBUG_PAGEALLOC and re-tested on 2.6.14-rc1.
> > > > Now the oops didn't happen when I connect digital camera to the USB.
> > >
> > > So the first oops was probably use-after-free.
> > >
> > > > I could mount the camera as USB storage.
> > > > But oops still happen when I turned the camera power off.
> > > > (This oops didn't halt my system, BTW)
> > > >
> > > > # Unable to handle kernel paging request at virtual address 6b6b6bb3
> > > > printing eip:
> > > > c02b88ca
> > > > *pde = 00000000
> > > > Oops: 0002 [#1]
> > > > SMP
> > > > Modules linked in: autofs e100 ipt_LOG ipt_state ip_conntrack
> > > > ipt_recent iptable_filter ip_tables video rtc
> > > > CPU: 0
> > > > EIP: 0060:[<c02b88ca>] Not tainted VLI
> > > > EFLAGS: 00010296 (2.6.14-rc1)
> > > > EIP is at scsi_remove_device+0x3a/0x50
> >
> > > > If you need some more test, let me know.
> > > > In that case, please specify which version of kernel you want me to test.
> > > >
> > >
> > > OK, thanks. This is a different bug. Presumably in USB.
> >
> > This was fixed in later releases of 2.6.14-rc.
> >
> > I wasn't able to reproduce the original problem, even after setting
> > CONFIG_DEBUG_PAGEALLOC.
> >
> > Alan Stern
> >
> Alan,
>
> Confirm the " scsi_remove_device " oops didn't happen on 2.4.14.
2.6.14, I assume.
> Talking about the original PANIC, as I have a workaround
> (CONFIG_DEBUG_PAGEALLOC disabled), I agree to close my report, now.
That's not a valid workaround. We're touching freed, unallocated or simply
wild memory and that is a bad bug.
next prev parent reply other threads:[~2005-11-02 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38bdcd1f0510290511t65bb16cfkfd1e84fb301424f9@mail.gmail.com>
2005-10-30 19:03 ` oops with USB Storage on 2.6.14 Andrew Morton
[not found] ` <38bdcd1f0510301641l3a211e41n3c571a98eef6185e@mail.gmail.com>
2005-10-31 1:02 ` Andrew Morton
2005-10-31 16:14 ` [linux-usb-devel] " Alan Stern
2005-11-02 2:56 ` Masanari Iida
2005-11-02 6:21 ` Andrew Morton [this message]
2005-11-08 4:40 ` Andrew Morton
2005-11-08 15:01 ` Masanari Iida
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=20051102172144.757fe643.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=standby24x7@gmail.com \
--cc=stern@rowland.harvard.edu \
/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