From: Randy Dunlap <randy.dunlap@Oracle.COM>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <jaxboe@fusionio.com>, Vivek Goyal <vgoyal@redhat.com>,
David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.37-rc1 (floppy module load: no device found)
Date: Fri, 05 Nov 2010 17:33:54 -0700 [thread overview]
Message-ID: <4CD4A272.8000000@oracle.com> (raw)
In-Reply-To: <AANLkTi=3f6f5MoZAX4C4ufYkopn8Z_xrR6nd-GzkoDhg@mail.gmail.com>
On 11/05/10 16:36, Linus Torvalds wrote:
> On Fri, Nov 5, 2010 at 4:03 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> On 11/05/10 15:10, Linus Torvalds wrote:
>>>
>>> Randy, is this one also related to that ipv6 percpu list corruption?
>>> IOW, does it go away with
>>>
>>> http://patchwork.ozlabs.org/patch/69939/
>>>
>>> like one of your other reports did?
>>
>> The list_debug.c message goes away, but it still gets the GP fault.
>
> Ok. I think there's a separate floppy.c bug introduced in commit
> 488211844e0c ("floppy: switch to one queue per drive instead of
> sharing a queue").
>
> We do "put_disk()" on the disk device _before_ we then clean up the
> queue associated with that disk.
>
> So maybe this trivial patch is in order?
>
> Again - UNTESTED. Jens, Vivek?
That survives load/unload 3 times.
Tested-by: Randy Dunlap <randy.dunlap@oracle.com>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-06 0:34 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 12:07 Linux 2.6.37-rc1 Linus Torvalds
2010-11-01 15:37 ` Thomas Gleixner
2010-11-01 15:47 ` Nick Bowler
2010-11-01 15:52 ` Ryusuke Konishi
2010-11-01 16:07 ` Linus Torvalds
2010-11-02 18:51 ` Linux 2.6.37-rc1 (acpi_video) Randy Dunlap
2010-11-03 21:08 ` Linux 2.6.37-rc1 (cciss: remove_proc_entry warning) Randy Dunlap
2010-11-03 21:15 ` Linux 2.6.37-rc1 (pcrypt fault) Randy Dunlap
2010-11-10 11:21 ` Steffen Klassert
2010-11-10 18:11 ` Randy Dunlap
2010-11-03 21:21 ` Linux 2.6.37-rc1 (net/sched: cls_cgroup) Randy Dunlap
2010-11-03 22:01 ` Eric Dumazet
2010-11-03 22:19 ` Li Zefan
2010-11-03 22:31 ` Li Zefan
2010-11-03 23:31 ` Herbert Xu
2010-11-04 1:46 ` Li Zefan
2010-11-04 1:56 ` David Miller
2010-11-04 15:56 ` Randy Dunlap
2010-11-03 23:16 ` Linux 2.6.37-rc1 (floppy module load: no device found) Randy Dunlap
2010-11-05 22:10 ` Linus Torvalds
2010-11-05 22:12 ` David Miller
2010-11-05 23:03 ` Randy Dunlap
2010-11-05 23:36 ` Linus Torvalds
2010-11-06 0:33 ` Randy Dunlap [this message]
2010-11-06 12:16 ` Vivek Goyal
2010-11-06 14:52 ` Linus Torvalds
2010-11-03 23:18 ` Linux 2.6.37-rc1 (libipw remove_proc_entry warning) Randy Dunlap
2010-11-05 22:24 ` Linus Torvalds
2010-11-05 23:06 ` Randy Dunlap
2010-11-05 23:38 ` Linus Torvalds
2010-11-08 21:33 ` John W. Linville
2010-11-03 23:20 ` Linux 2.6.37-rc1 (scsi_debug: list corruption) Randy Dunlap
2010-11-04 2:25 ` Xiaotian Feng
2010-11-04 16:12 ` Randy Dunlap
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=4CD4A272.8000000@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
/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