From: James Bottomley <James.Bottomley@steeleye.com>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: James.Bottomley@SteelEye.com, linux-kernel@vger.kernel.org,
sullivan@austin.ibm.com
Subject: [BUG-2.5.24-BK] DriverFS panics on boot!
Date: Thu, 04 Jul 2002 11:41:22 -0400 [thread overview]
Message-ID: <200207041541.g64FfNW02097@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Er, oops, I think this one's my fault.
The recent driverfs additions for SCSI also added partition handling in
driverfs. The code is slightly more invasive than it should be so the IDE
driver needs to know how to use it (which it doesn't yet). In theory there's
a NULL pointer check in driverfs_create_partitions for precisely this case,
but it looks like the IDE code is forgetting to zero out a kmalloc of a struct
gendisk somewhere (hence the 5a5a... contents). At a cursory glance, this
seems to be in ide/probe.c, so does the attached patch fix it?
I'll try to reproduce, but I'm all SCSI here except for my laptop.
James
[-- Attachment #2: tmp.diff --]
[-- Type: text/plain , Size: 366 bytes --]
===== drivers/ide/probe.c 1.58 vs edited =====
--- 1.58/drivers/ide/probe.c Fri Jun 14 09:11:19 2002
+++ edited/drivers/ide/probe.c Thu Jul 4 10:31:35 2002
@@ -1143,6 +1143,7 @@
if (!gd)
goto err_kmalloc_gd;
+ memset(gd, 0, sizeof(struct gendisk));
gd->sizes = kmalloc(ATA_MINORS * sizeof(int), GFP_KERNEL);
if (!gd->sizes)
goto err_kmalloc_gd_sizes;
next reply other threads:[~2002-07-04 15:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 15:41 James Bottomley [this message]
2002-07-04 15:55 ` Anton Altaparmakov
2002-07-04 22:20 ` Andre Hedrick
2002-07-04 22:59 ` James Bottomley
2002-07-05 2:15 ` Andre Hedrick
2002-07-05 6:34 ` Jens Axboe
2002-07-05 6:51 ` Andre Hedrick
2002-07-05 7:38 ` Jens Axboe
2002-07-05 22:43 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 11:28 Anton Altaparmakov
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=200207041541.g64FfNW02097@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sullivan@austin.ibm.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
all inboxes | Powered by JetHome®