public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Go Taniguchi <go@turbolinux.co.jp>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH]initrd unmount problem
Date: Mon, 28 May 2001 13:26:20 +0900	[thread overview]
Message-ID: <3B11D36C.2967AFDC@turbolinux.co.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

Hi,

It seems that ioctl_by_bdev() in fs/block_dev.c has a problem.
When initrd is unmounted it can cause OOPS. 
This problem occurs in recent ac patches.
May be vanilla too.

change_root() in fs/super.c calls ioctl_by_bdev() in
fs/block_dev.c which does not set inode_fake.i_bdev.

But ioctl of ramdisk (rd_ioctl() in rd.c) accesses to
i_bdev->bd_openers of the inode and which causes OOPS.

I attach the patch.

- GO!

[-- Attachment #2: block_dev.c.patch --]
[-- Type: text/plain, Size: 344 bytes --]

--- linux/fs/block_dev.c.orig	Mon May 28 12:40:12 2001
+++ linux/fs/block_dev.c	Mon May 28 12:40:12 2001
@@ -602,6 +602,7 @@
 	if (!bdev->bd_op->ioctl)
 		return -EINVAL;
 	inode_fake.i_rdev=rdev;
+	inode_fake.i_bdev=bdev;
 	init_waitqueue_head(&inode_fake.i_wait);
 	set_fs(KERNEL_DS);
 	res = bdev->bd_op->ioctl(&inode_fake, NULL, cmd, arg);

                 reply	other threads:[~2001-05-28  4:26 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=3B11D36C.2967AFDC@turbolinux.co.jp \
    --to=go@turbolinux.co.jp \
    --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