From: Jan Kara <jack@suse.cz>
To: <linux-block@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
Hou Tao <houtao1@huawei.com>, Eric Biggers <ebiggers3@gmail.com>,
Jan Kara <jack@suse.cz>
Subject: [PATCH 0/6] block: Fix races in bdev - gendisk handling
Date: Tue, 6 Feb 2018 17:05:23 +0100 [thread overview]
Message-ID: <20180206160529.20713-1-jack@suse.cz> (raw)
Hello,
these patches fix races happening when devices are frequently destroyed and
recreated in association of block device inode with corresponding gendisk.
Generally when such race happen it results in use-after-free issues, block
device page cache inconsistencies, or other problems. I have verified these
patches fix use-after-free issues that could be reproduced by frequent creation
and destruction of loop device. I was not able to reproduce races reported by
Hou Tao [1] related to gendisk-blkdev association (at least I was not able to
hit any issues with stressing using scsi_debug in various ways with or without
patches). My patches should fix those but it would be great if Tao could verify
that. Any comments and review welcome!
Honza
[1] https://www.spinics.net/lists/linux-block/msg20015.html
next reply other threads:[~2018-02-06 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 16:05 Jan Kara [this message]
2018-02-06 16:05 ` [PATCH 1/6] genhd: Fix leaked module reference for NVME devices Jan Kara
2018-02-06 16:05 ` [PATCH 2/6] genhd: Rename get_disk() to get_disk_and_module() Jan Kara
2018-02-06 16:05 ` [PATCH 3/6] genhd: Add helper put_disk_and_module() Jan Kara
2018-02-06 16:05 ` [PATCH 4/6] genhd: Fix use after free in __blkdev_get() Jan Kara
2018-02-13 2:11 ` Hou Tao
2018-02-06 16:05 ` [PATCH 5/6] genhd: Fix BUG in blkdev_open() Jan Kara
2018-02-13 2:11 ` Hou Tao
2018-02-14 11:53 ` Jan Kara
2018-02-06 16:05 ` [PATCH 6/6] blockdev: Avoid two active bdev inodes for one device Jan Kara
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=20180206160529.20713-1-jack@suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=ebiggers3@gmail.com \
--cc=houtao1@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=tj@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).