From: Boaz Harrosh <bharrosh@panasas.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: schwidefsky@de.ibm.com, Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
linux-kernel@vger.kernel.org, j-nomura@ce.jp.nec.com,
jens.axboe@oracle.com, m-ikeda@ds.jp.nec.com
Subject: Re: kernel BUG at drivers/block/ub.c:820!
Date: Thu, 03 Apr 2008 20:36:38 +0300 [thread overview]
Message-ID: <47F515A6.4040505@panasas.com> (raw)
In-Reply-To: <20080403093042.f20e38a2.zaitcev@redhat.com>
On Thu, Apr 03 2008 at 19:30 +0300, Pete Zaitcev <zaitcev@redhat.com> wrote:
> On Thu, 03 Apr 2008 17:18:31 +0200, Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
>> On Thu, 2008-04-03 at 11:08 -0500, Kiyoshi Ueda wrote:
>
>>> I believe the patch from Pete fixes this BUG():
>>> http://marc.info/?l=linux-usb&m=120613888005382&w=2
>>>
>>> Could you try that?
>> Just tested the patch and it indeed fixes the bug.
>
> I'm glad.
>
>> Could we push this upstream for 2.6.25? It is a regression, I would
>> prefer to have a 2.6.25 that doesn't panic my machine when I attach a
>> USB stick..
>
> I was going to work through Greg as usual and then push it to
> the stable tree. I'm not Linus' "leutenant", so I cannot just send
> him random patches.
>
> -- Pete
This is a block device siting in block/ folder. It is certainly Jens's
linux-block territory. Best put it through the tree that introduced the
bug, no?
Best would be to resend to Jens ASAP, it is a 2.6.25 regression.
Boaz
next prev parent reply other threads:[~2008-04-03 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 8:42 kernel BUG at drivers/block/ub.c:820! Martin Schwidefsky
2008-04-03 11:32 ` Boaz Harrosh
2008-04-03 13:57 ` Martin Schwidefsky
2008-04-03 14:15 ` Boaz Harrosh
2008-04-03 15:02 ` Martin Schwidefsky
2008-04-03 16:08 ` Kiyoshi Ueda
2008-04-03 15:18 ` Martin Schwidefsky
2008-04-03 16:30 ` Pete Zaitcev
2008-04-03 17:36 ` Boaz Harrosh [this message]
2008-04-04 4:30 ` Andrew Morton
2008-04-04 15:29 ` Kiyoshi Ueda
2008-04-04 19:45 ` Pete Zaitcev
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=47F515A6.4040505@panasas.com \
--to=bharrosh@panasas.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jens.axboe@oracle.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-ikeda@ds.jp.nec.com \
--cc=schwidefsky@de.ibm.com \
--cc=zaitcev@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