From: John Byrne <john.l.byrne@compaq.com>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: linux-kernel@vger.kernel.org
Subject: Change in add_gendisk() in 2.4.11-preXXX
Date: Fri, 05 Oct 2001 11:02:32 -0700 [thread overview]
Message-ID: <3BBDF5B8.A6B649A3@compaq.com> (raw)
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. 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".
So, my question to you or anyone is, is anyone looking further at the
causes of the problem right now?
John Byrne
next reply other threads:[~2001-10-05 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 18:02 John Byrne [this message]
2001-10-05 18:07 ` Change in add_gendisk() in 2.4.11-preXXX Christoph Hellwig
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=3BBDF5B8.A6B649A3@compaq.com \
--to=john.l.byrne@compaq.com \
--cc=hch@ns.caldera.de \
--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