From: viro@parcelfarce.linux.theplanet.co.uk
To: linux-kernel@vger.kernel.org
Cc: mikem@beardog.cca.cpqcorp.net
Subject: [CFT][PATCH] cciss/cpqarray fixes (2.5)
Date: Sat, 26 Apr 2003 04:41:51 +0100 [thread overview]
Message-ID: <20030426034151.GM10374@parcelfarce.linux.theplanet.co.uk> (raw)
Folks, if you have access to cciss and/or cpqarray test boxen,
please check if ftp.linux.org.uk/pub/people/viro/T24-cciss-C68 and
ftp.linux.org.uk/pub/people/viro/T25-cpqarray-C68 restore the "allow
root to open device with minor 0 even if nothing had been configured"
behaviour.
Changes:
a) we _always_ register gendisk for disk #0 on controller.
b) it stays registered until we forget about controller.
c) when old code would remove it, we merely set size to 0.
That (presumably) fixes the breakage introduced in 2.5 when we
started to require registered gendisk for open(2). Please, check if that
helps and doesn't introduce new breakage - I don't have either hardware, so
it's completely untested. It builds, but that's it.
reply other threads:[~2003-04-26 3:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030426034151.GM10374@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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;
as well as URLs for NNTP newsgroup(s).