public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: John Byrne <john.l.byrne@compaq.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Change in add_gendisk() in 2.4.11-preXXX
Date: Fri, 5 Oct 2001 20:07:35 +0200	[thread overview]
Message-ID: <20011005200735.A22840@caldera.de> (raw)
In-Reply-To: <3BBDF5B8.A6B649A3@compaq.com>
In-Reply-To: <3BBDF5B8.A6B649A3@compaq.com>; from john.l.byrne@compaq.com on Fri, Oct 05, 2001 at 11:02:32AM -0700

On Fri, Oct 05, 2001 at 11:02:32AM -0700, John Byrne wrote:
> 
> Cristoph,
> 
> Looking in the Changelog for 2.4.11-pre, I find that you are given
> credit for the change to add_gendisk() which should prevent the
> /proc/paritions loop; which is good.

In fact it was Alan's fix, I just sent it to Linus 8)

> However, I was tracing the bug
> myself and come to the conclusion the culprit in my case was the "sd"
> driver. One of our systems has two different SCSI HBAs and this resulted
> in two calls to sd_finish() which results in the sd_gendisk structures
> being added twice and, hence, the loop. So, I am a little concerned that
> your change is covering up the problem so well, that the actual issue
> may not be addressed. Unfortunately, I don't understand the ins and outs
> of the SCSI and blkdev layers to suggest a fix for "sd".

If you look at the new add_gendisk structure it is clearly marked that
the new bahaviour is a workaround.

It will be fixed in 2.5, but the scsi layer is too fragile to do such
changes in 2.4.

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

      reply	other threads:[~2001-10-05 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 18:02 Change in add_gendisk() in 2.4.11-preXXX John Byrne
2001-10-05 18:07 ` Christoph Hellwig [this message]

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=20011005200735.A22840@caldera.de \
    --to=hch@ns.caldera.de \
    --cc=john.l.byrne@compaq.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