From: Matthias Urlichs <smurf@smurf.noris.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6: Crash when calling "blockdev --rereadpt" on USB insert
Date: Sun, 7 Sep 2003 05:29:55 +0200 [thread overview]
Message-ID: <200309070529.55502@smurf.noris.de> (raw)
I have this snippet in my /etc/hotplug/usb script to mount my USB disk
when I insert it:
if [ "$PRODUCT" = "58f/9380/100" ]; then
find /dev/scsi -name disc | while read a ; do
/sbin/blockdev --rereadpt $a
done
if sudo -u smurf mount /mnt/key ; then
echo "#!/bin/sh" > $REMOVER
echo "umount -f /mnt/key" >> $REMOVER
chmod +x $REMOVER
fi
fi
This works splendidly with 2.4, but 2.6.0.test4 (where it's arguably
unnecessary...) dies with this message:
Sep 7 05:18:38 linux kernel: Oops: kernel access of bad area, sig: 11 [#1]
Sep 7 05:18:38 linux kernel: NIP: C001407C LR: C0072830 SP: DD749DA0 REGS: dd749cf0 TRAP: 0301 Not tainted
Sep 7 05:18:38 linux kernel: MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
Sep 7 05:18:38 linux kernel: DAR: FFFFFFEF, DSISR: 40000000
Sep 7 05:18:38 linux kernel: TASK = caf46940[4768] 'blockdev' Last syscall: 54
Sep 7 05:18:38 linux kernel: GPR00: C0072830 DD749DA0 CAF46940 FFFFFFEF C0293B30 C00930F0 D56A4EFF DD748000
Sep 7 05:18:38 linux kernel: GPR08: C0940000 00000000 00000002 DD748000 82000228
Sep 7 05:18:38 linux kernel: Call trace:
Sep 7 05:18:38 linux kernel: [c0072830] dput+0x2c/0x300
Sep 7 05:18:38 linux kernel: [c00931f4] create_dir+0xd4/0xe8
Sep 7 05:18:38 linux kernel: [c0093254] sysfs_create_dir+0x40/0xa4
Sep 7 05:18:38 linux kernel: [c00c0480] create_dir+0x28/0x6c
Sep 7 05:18:38 linux kernel: [c00c09f4] kobject_add+0xdc/0x194
Sep 7 05:18:38 linux kernel: [c00c0ad8] kobject_register+0x2c/0x6c
Sep 7 05:18:38 linux kernel: [c00907d8] add_partition+0xb8/0xdc
Sep 7 05:18:38 linux kernel: [c0090aa8] rescan_partitions+0xf0/0x128
Sep 7 05:18:38 linux kernel: [c00f0ca8] blkdev_reread_part+0x94/0xc4
Sep 7 05:18:38 linux kernel: [c00f0f14] blkdev_ioctl+0x160/0x450
Sep 7 05:18:38 linux kernel: [c006d548] sys_ioctl+0x144/0x364
Sep 7 05:18:38 linux kernel: [c0007b8c] ret_from_syscall+0x0/0x4c
This doesn't look like it's PPC specific. I can probably reproduce on
i386 if that would be helpful to anybody.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
It is better to decide between our enemies than our friends; for one of our
friends will most likely become our enemy; but on the other hand, one of your
enemies will probably become your friend.
-- Bias
reply other threads:[~2003-09-07 3:38 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=200309070529.55502@smurf.noris.de \
--to=smurf@smurf.noris.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;
as well as URLs for NNTP newsgroup(s).