From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@infradead.org>, axboe@kernel.dk
Cc: Mikulas Patocka <mpatocka@redhat.com>,
dm-devel@redhat.com, "Alasdair G. Kergon" <agk@redhat.com>,
linux-block@vger.kernel.org
Subject: [PATCH] brd: remove support for BLKFLSBUF
Date: Tue, 25 Oct 2016 10:37:19 -0400 [thread overview]
Message-ID: <20161025143719.GA51266@redhat.com> (raw)
In-Reply-To: <20161025130712.GA12717@infradead.org>
On Tue, Oct 25 2016 at 9:07P -0400,
Christoph Hellwig <hch@infradead.org> wrote:
> I think the right fix is to kill off the BLKFLSBUF special case in
> brd. Yes, it break compatibility - but in this case the compatibility
> breaks more than it helps.
Jens, please pick up this patch:
From: Mike Snitzer <snitzer@redhat.com>
Date: Tue, 25 Oct 2016 10:25:07 -0400
Subject: [PATCH] brd: remove support for BLKFLSBUF
Discontinue having the brd driver destructively free all pages in the
ramdisk in response to the BLKFLSBUF ioctl. Doing so allows a BLKFLSBUF
ioctl issued to a logical partition to destroy pages of the parent brd
device (and all other partitions of that brd device).
This change breaks compatibility - but in this case the compatibility
breaks more than it helps.
Reported-by: Mikulas Patocka <mpatocka@redhat.com>
Suggested-by: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
---
drivers/block/brd.c | 35 -----------------------------------
1 file changed, 35 deletions(-)
diff --git a/drivers/block/brd.c b/drivers/block/brd.c
index 0c76d40..45c998a 100644
--- a/drivers/block/brd.c
+++ b/drivers/block/brd.c
@@ -395,44 +395,9 @@ static long brd_direct_access(struct block_device *bdev, sector_t sector,
#define brd_direct_access NULL
#endif
-static int brd_ioctl(struct block_device *bdev, fmode_t mode,
- unsigned int cmd, unsigned long arg)
-{
- int error;
- struct brd_device *brd = bdev->bd_disk->private_data;
-
- if (cmd != BLKFLSBUF)
- return -ENOTTY;
-
- /*
- * ram device BLKFLSBUF has special semantics, we want to actually
- * release and destroy the ramdisk data.
- */
- mutex_lock(&brd_mutex);
- mutex_lock(&bdev->bd_mutex);
- error = -EBUSY;
- if (bdev->bd_openers <= 1) {
- /*
- * Kill the cache first, so it isn't written back to the
- * device.
- *
- * Another thread might instantiate more buffercache here,
- * but there is not much we can do to close that race.
- */
- kill_bdev(bdev);
- brd_free_pages(brd);
- error = 0;
- }
- mutex_unlock(&bdev->bd_mutex);
- mutex_unlock(&brd_mutex);
-
- return error;
-}
-
static const struct block_device_operations brd_fops = {
.owner = THIS_MODULE,
.rw_page = brd_rw_page,
- .ioctl = brd_ioctl,
.direct_access = brd_direct_access,
};
--
2.8.4 (Apple Git-73)
next prev parent reply other threads:[~2016-10-25 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 18:33 device mapper and the BLKFLSBUF ioctl Mikulas Patocka
2016-10-21 20:00 ` Mike Snitzer
2016-10-21 20:18 ` Mikulas Patocka
2016-10-24 15:57 ` Mike Snitzer
2016-10-25 13:07 ` Christoph Hellwig
2016-10-25 14:37 ` Mike Snitzer [this message]
2016-10-25 14:46 ` [PATCH] brd: remove support for BLKFLSBUF Jens Axboe
2016-10-26 20:25 ` [PATCH 0/4] brd: support discard Mikulas Patocka
2016-10-26 20:26 ` [PATCH 1/4] brd: handle misaligned discard Mikulas Patocka
2016-10-26 20:38 ` [dm-devel] " Bart Van Assche
2016-10-26 21:46 ` Mikulas Patocka
2016-10-26 21:50 ` REQ_OP for zeroing, was " Christoph Hellwig
2016-10-28 11:43 ` Mikulas Patocka
2016-10-28 13:14 ` Christoph Hellwig
2016-10-31 16:36 ` Mikulas Patocka
2016-10-26 21:57 ` Bart Van Assche
2016-10-28 11:39 ` Mikulas Patocka
2016-10-28 15:55 ` Bart Van Assche
2016-10-31 16:31 ` Mikulas Patocka
2016-10-26 20:26 ` [PATCH 2/4] brd: extend rcu read sections Mikulas Patocka
2016-10-26 20:27 ` [PATCH 3/4] brd: implement discard Mikulas Patocka
2016-10-26 20:27 ` [PATCH 4/4] brd: remove unused brd_zero_page Mikulas Patocka
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=20161025143719.GA51266@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.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;
as well as URLs for NNTP newsgroup(s).