From: Nathan Scott <nathans@sgi.com>
To: akpm@osdl.org, torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] blkdev_open/bd_claim vs BLKBSZSET
Date: Tue, 24 Feb 2004 10:17:05 +1100 [thread overview]
Message-ID: <20040223231705.GB773@frodo> (raw)
Hi there,
I was modifying mkfs.xfs to use O_EXCL for 2.6, and hit a snag.
It seems that once I've opened a block dev with O_EXCL I can no
longer issue the BLKBSZSET ioctl to it. (Is that the expected
behavior? If so, ignore...)
The fs/block_dev.c code for blkdev_open does:
int blkdev_open(struct inode * inode, struct file * filp)
...
if (!(res = bd_claim(bdev, filp)))
return 0;
And the drivers/block/ioctl.c code for BLKBSZSET does this:
int holder;
...
case BLKBSZSET:
...
if (bd_claim(bdev, &holder) < 0)
return -EBUSY;
ret = set_blocksize(bdev, n);
bd_release(bdev);
And mkfs gets EBUSY back from the ioctl. Using the patch
below, the ioctl succeeds cos the original filp bdev owner
from open now matches with the owner in the ioctl call. I
suspect that would be the correct behavior, but perhaps I'm
overlooking some good reason for it being this way?
cheers.
--
Nathan
--- /usr/tmp/TmpDir.4274-0/drivers/block/ioctl.c_1.1 2004-02-24 08:58:28.000000000 +1100
+++ drivers/block/ioctl.c 2004-02-23 20:12:24.216909064 +1100
@@ -138,7 +138,6 @@
struct block_device *bdev = inode->i_bdev;
struct gendisk *disk = bdev->bd_disk;
struct backing_dev_info *bdi;
- int holder;
int ret, n;
switch (cmd) {
@@ -175,7 +174,7 @@
return -EINVAL;
if (get_user(n, (int *) arg))
return -EFAULT;
- if (bd_claim(bdev, &holder) < 0)
+ if (bd_claim(bdev, file) < 0)
return -EBUSY;
ret = set_blocksize(bdev, n);
bd_release(bdev);
next reply other threads:[~2004-02-23 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 23:17 Nathan Scott [this message]
2004-02-23 23:28 ` [PATCH] blkdev_open/bd_claim vs BLKBSZSET viro
2004-02-23 23:53 ` Nathan Scott
2004-02-24 0:54 ` viro
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=20040223231705.GB773@frodo \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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