public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Doug Ledford <dledford@redhat.com>,
	Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: smp dead lock of io_request_lock/queue_lock patch
Date: Fri, 16 Jan 2004 10:40:21 -0500	[thread overview]
Message-ID: <400805E5.9070808@tmr.com> (raw)
In-Reply-To: <1elvB-Jt-25@gated-at.bofh.it>

Doug Ledford wrote:
> On Thu, 2004-01-15 at 12:01, Bill Davidsen wrote:

>>"not in a released kernel..." Do I read this right? That you have a fix 
>>for a critical bug and it hasn't been pushed to customers yet?
> 
> 
> No, you don't read this right.  We have a fix for a correctness issue
> that has almost 0% chance of ever triggering in real life, has exactly 0
> bug reports of it ever happening, and which has been integrated into our
> tree.  Obviously, we always push new kernels to all of our customers
> every time we have this situation, or about twice a day...

I actually had in mind a notification so customers would know it was 
there if they actually see a similar problem, and a way to get the fix 
if needed. Since a patch was posted, I assume that's it's not quite as 
unlikely as you seem to imply.

We have two copies of RHEL-3.0 in-house, and I have a budget line item 
to upgrade 38 servers from RH-8.0 this year. Since they are all SMP/SCSI 
I think my concern with this bug, and the bug notification process in 
general is germane. I don't want to apply fixes for problems I don't 
have, but I want to know what fixes are out there so if I have a similar 
problem I can apply the fix(es) which might be related before spending a 
lot of time chasing the problem.

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

       reply	other threads:[~2004-01-16 15:41 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1d6yN-6HH-17@gated-at.bofh.it>
     [not found] ` <1dasC-5Ww-5@gated-at.bofh.it>
     [not found]   ` <1ejkf-724-13@gated-at.bofh.it>
     [not found]     ` <1elvB-Jt-25@gated-at.bofh.it>
2004-01-16 15:40       ` Bill Davidsen [this message]
2004-01-19 21:36 smp dead lock of io_request_lock/queue_lock patch Martin Peschke3
2004-03-08 21:25 ` Doug Ledford
  -- strict thread matches above, loose matches on Subject: below --
2004-01-12 16:32 Peter Yao
2004-01-12  9:08 ` Arjan van de Ven
2004-01-12  9:19   ` Jens Axboe
2004-01-12  9:19     ` Jens Axboe
2004-01-12  9:20       ` Arjan van de Ven
2004-01-12  9:22         ` Jens Axboe
2004-01-12 13:27           ` Doug Ledford
2004-01-15 17:01             ` Bill Davidsen
2004-01-15 17:05               ` Jens Axboe
2004-01-15 17:09               ` Arjan van de Ven
2004-01-15 19:30               ` Doug Ledford
2004-01-12 15:07 Martin Peschke3
2004-01-12 15:12 ` Arjan van de Ven
2004-01-12 19:48   ` Christoph Hellwig
2004-01-12 19:51     ` Doug Ledford
2004-01-12 20:03       ` Christoph Hellwig
2004-01-12 21:12         ` Jens Axboe
2004-01-13 20:55       ` Marcelo Tosatti
2004-01-17 13:10         ` Doug Ledford
2004-01-17 16:58           ` Christoph Hellwig
2004-01-17 19:07             ` Doug Ledford
2004-01-17 19:17               ` Christoph Hellwig
2004-01-17 19:21                 ` Doug Ledford
2004-01-17 19:29                   ` Christoph Hellwig
2004-01-17 20:36                     ` Doug Ledford
2004-01-20  7:53               ` Jens Axboe
2004-01-25  0:31           ` Kurt Garloff
2004-01-15 17:17       ` Bill Davidsen
2004-01-17 13:12         ` Doug Ledford
2004-01-17 15:16           ` Bill Davidsen
2004-01-17 16:07             ` Doug Ledford
2004-01-12 14:07 Martin Peschke3
2004-01-12 14:11 ` Arjan van de Ven
2004-01-12 14:13 ` Jens Axboe
2004-01-12 15:08   ` Doug Ledford
2004-01-12 15:24     ` James Bottomley
2004-01-12 15:43       ` Jens Axboe
2004-01-12 15:52         ` Doug Ledford
2004-01-12 16:04           ` James Bottomley
2004-01-12 16:05             ` Doug Ledford

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=400805E5.9070808@tmr.com \
    --to=davidsen@tmr.com \
    --cc=dledford@redhat.com \
    --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