From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Yufen Yu <yuyufen@huawei.com>,
Christoph Hellwig <hch@infradead.org>,
Hou Tao <houtao1@huawei.com>
Subject: [PATCH V3 0/4] block: fix partition use-after-free and optimization
Date: Fri, 8 May 2020 16:17:54 +0800 [thread overview]
Message-ID: <20200508081758.1380673-1-ming.lei@redhat.com> (raw)
Hi,
The 1st patch fixes one use-after-free on cached last_lookup partition.
The other 3 patches optimizes partition uses in IO path.
V3:
- add reviewed-by tag
- centralize partno check in the helper(4/4)
V2:
- add comment, use part_to_disk() to retrieve disk instead of
adding one field to hd_struct
- don't put part in blk_account_io_merge
Ming Lei (4):
block: fix use-after-free on cached last_lookup partition
block: only define 'nr_sects_seq' in hd_part for 32bit SMP
block: re-organize fields of 'struct hd_part'
block: don't hold part0's refcount in IO path
block/blk-core.c | 12 ------------
block/blk.h | 13 ++++++-------
block/genhd.c | 17 +++++++++++++----
block/partitions/core.c | 14 ++++++++++++--
include/linux/genhd.h | 24 +++++++++++++++++-------
5 files changed, 48 insertions(+), 32 deletions(-)
Cc: Yufen Yu <yuyufen@huawei.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Hou Tao <houtao1@huawei.com>
--
2.25.2
next reply other threads:[~2020-05-08 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 8:17 Ming Lei [this message]
2020-05-08 8:17 ` [PATCH V3 1/4] block: fix use-after-free on cached last_lookup partition Ming Lei
2020-05-08 8:17 ` [PATCH V3 2/4] block: only define 'nr_sects_seq' in hd_part for 32bit SMP Ming Lei
2020-05-08 8:17 ` [PATCH V3 3/4] block: re-organize fields of 'struct hd_part' Ming Lei
2020-05-08 8:17 ` [PATCH V3 4/4] block: don't hold part0's refcount in IO path Ming Lei
2020-05-12 2:44 ` [PATCH V3 0/4] block: fix partition use-after-free and optimization Ming Lei
2020-05-13 2:32 ` Jens Axboe
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=20200508081758.1380673-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=houtao1@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=yuyufen@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.