From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ewan D . Milne" <emilne@redhat.com>
Subject: Re: [PATCH 0/2] block: avoid to drop & re-add partitions if partitions aren't changed
Date: Mon, 15 Feb 2021 12:03:41 +0800 [thread overview]
Message-ID: <20210215040341.GA257964@T590> (raw)
In-Reply-To: <20210205021708.1498711-1-ming.lei@redhat.com>
On Fri, Feb 05, 2021 at 10:17:06AM +0800, Ming Lei wrote:
> Hi Guys,
>
> The two patches changes block ioctl(BLKRRPART) for avoiding drop &
> re-add partitions if partitions state isn't changed. The current
> behavior confuses userspace because partitions can disappear anytime
> when ioctl(BLKRRPART).
>
> Ming Lei (2):
> block: move partitions check code into single helper
> block: avoid to drop & re-add partitions if partitions aren't changed
>
> block/genhd.c | 2 +
> block/partitions/check.h | 2 +
> block/partitions/core.c | 101 ++++++++++++++++++++++++++++++++-------
> fs/block_dev.c | 28 +++++++++--
> include/linux/genhd.h | 4 ++
> 5 files changed, 118 insertions(+), 19 deletions(-)
>
> Cc: Ewan D. Milne <emilne@redhat.com>
> --
> 2.29.2
>
Hello,
Ping...
--
Ming
next prev parent reply other threads:[~2021-02-15 4:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 2:17 [PATCH 0/2] block: avoid to drop & re-add partitions if partitions aren't changed Ming Lei
2021-02-05 2:17 ` [PATCH 1/2] block: move partitions check code into single helper Ming Lei
2021-02-05 2:17 ` [PATCH 2/2] block: avoid to drop & re-add partitions if partitions aren't changed Ming Lei
2021-02-05 7:14 ` Christoph Hellwig
2021-02-05 7:30 ` Ming Lei
2021-02-15 4:03 ` Ming Lei [this message]
2021-02-16 8:44 ` [PATCH 0/2] " Christoph Hellwig
2021-02-17 3:07 ` Ming Lei
2021-02-17 7:16 ` Christoph Hellwig
2021-02-18 7:57 ` Ming Lei
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=20210215040341.GA257964@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).