mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Takashi Iwai" <tiwai@suse.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Edgar Kalkowski" <eMail@edgar-kalkowski.de>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: PROBLEM: Kernel 2.6.26 oops if I unplug my Logitech USB 1.1 headset
Date: Fri, 5 Sep 2008 10:18:06 +0200	[thread overview]
Message-ID: <19f34abd0809050118g38c87ca5i56fb3cc6d01b7f1a@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0809050101h2b207d19k9d1bd67351499385@mail.gmail.com>

On Fri, Sep 5, 2008 at 10:01 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> On Fri, Sep 5, 2008 at 9:58 AM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
>> On Fri, Sep 5, 2008 at 9:09 AM, Takashi Iwai <tiwai@suse.de> wrote:
>>> At Thu, 4 Sep 2008 17:28:22 -0700,
>>> Andrew Morton wrote:
>>>>
>>>> On Fri, 05 Sep 2008 01:05:21 +0200
>>>> Edgar Kalkowski <eMail@edgar-kalkowski.de> wrote:
>>>>
>>>> > Dear kernel hackers. ;)
>>>> >
>>>> > [1.] One line summary of the problem: If I unplug my USB-Headset the kernel oopses.
>>>>
>>>> cc's added.
>>>>
>>>> Might be USB, might be ALSA.
>>>
>>> Hm, it's hard to guess...
>>> Edgar, could you check whether it happens with 2.6.25?
>>
>> Hi,
>>
>> I recognize this address:
>>
>>>>> BUG: unable to handle kernel paging request at 00100100
>>
>> Is this a magic value? I also got it, see for example:
>> http://lkml.org/lkml/2008/8/21/426
>>
>> Google will also recognize it:
>> http://www.google.com/search?hl=en&q="unable+to+handle+kernel+paging+request"+00100100
>>
>> Where does it come from?
>
> Oh. It _is_ LIST_POISON1. Sorry for the bit of noise.

Probably totally unrelated, but I couldn't help to find this bit of
code somewhat odd. In snd_ctl_dev_disconnect():

        down_read(&card->controls_rwsem);
        list_for_each_entry(ctl, &card->ctl_files, list) {
                wake_up(&ctl->change_sleep);
                kill_fasync(&ctl->fasync, SIGIO, POLL_ERR);
        }
        up_read(&card->controls_rwsem);

...shouldn't that be using &card->ctl_files_rwlock instead of
&card->controls_rwsem? That one is always used to protect the list ops
on &card->ctl_files in all the other places. Or maybe it is already
locked from higher ups?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

  reply	other threads:[~2008-09-05  8:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04 23:05 Edgar Kalkowski
2008-09-05  0:28 ` Andrew Morton
2008-09-05  7:09   ` Takashi Iwai
2008-09-05  7:58     ` Vegard Nossum
2008-09-05  8:01       ` Vegard Nossum
2008-09-05  8:18         ` Vegard Nossum [this message]
2008-09-07  9:56           ` Takashi Iwai
2008-09-10  7:43     ` Edgar Kalkowski

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=19f34abd0809050118g38c87ca5i56fb3cc6d01b7f1a@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=eMail@edgar-kalkowski.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®