From: Jens Axboe <axboe@kernel.dk>
To: Dongli Zhang <dongli.zhang@oracle.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jack@suse.cz
Subject: Re: [PATCH v3 0/2] loop: fix two issues introduced by prior commit
Date: Fri, 22 Feb 2019 15:51:43 -0700 [thread overview]
Message-ID: <4ffc6fe4-5baf-a502-6042-d4f5033c4cc7@kernel.dk> (raw)
In-Reply-To: <1550844620-6550-1-git-send-email-dongli.zhang@oracle.com>
On 2/22/19 7:10 AM, Dongli Zhang wrote:
> This patch set fix two issues introduced by prior commit.
>
>
> [PATCH v3 1/2] loop: do not print warn message if partition scan is successful
> [PATCH v3 1/2] fixes d57f3374ba48 ("loop: Move special partition reread
> handling in loop_clr_fd()") to not always print warn message even when
> partition scan is successful.
>
>
> [PATCH v3 2/2] loop: set GENHD_FL_NO_PART_SCAN after blkdev_reread_part()
> [PATCH v3 2/2] fixes 0da03cab87e6 ("loop: Fix deadlock when calling
> blkdev_reread_part()") to not set GENHD_FL_NO_PART_SCAN before partition
> scan when detaching loop device from the file.
>
> Changed since v1:
> * move the setting of lo->lo_state to Lo_unbound after partscan has finished as well
> (suggested by Jan Kara)
>
> Changed since v2:
> * Put the code inline in __loop_clr_fd() but not introduce new function
> (suggested by Jan Kara)
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2019-02-22 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 14:10 Dongli Zhang
2019-02-22 14:10 ` [PATCH v3 1/2] loop: do not print warn message if partition scan is successful Dongli Zhang
2019-02-22 14:10 ` [PATCH v3 2/2] loop: set GENHD_FL_NO_PART_SCAN after blkdev_reread_part() Dongli Zhang
2019-02-22 22:51 ` Jens Axboe [this message]
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=4ffc6fe4-5baf-a502-6042-d4f5033c4cc7@kernel.dk \
--to=axboe@kernel.dk \
--cc=dongli.zhang@oracle.com \
--cc=jack@suse.cz \
--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
all inboxes | Powered by JetHome®