From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>
Cc: Tejun Heo <tj@kernel.org>,
linux-block@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Omar Sandoval <osandov@osandov.com>,
Arthur Marsh <arthur.marsh@internode.on.net>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/4 v2] block: Fixes for bdi handling
Date: Thu, 9 Mar 2017 09:41:01 -0700 [thread overview]
Message-ID: <7177cebf-8a9b-10d4-e991-5e43f4303ffc@kernel.dk> (raw)
In-Reply-To: <20170309101624.25901-1-jack@suse.cz>
On 03/09/2017 03:16 AM, Jan Kara wrote:
> Hi!
>
> this is a second revision of the series fixing the most urgent bugs that were
> introduced by commit 165a5e22fafb "block: Move bdi_unregister() to
> del_gendisk()" and by 0dba1314d4f8 "scsi, block: fix duplicate bdi name
> registration crashes". In fact before these commits we had a different set of
> problems in the code but they were less visible :).
It was rather urgent to get those fixes in, so I already sent them off. Not a
huge deal, but it would be nice to add the atomic init fix as a separate patch
later on.
--
Jens Axboe
next prev parent reply other threads:[~2017-03-09 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 10:16 [PATCH 0/4 v2] block: Fixes for bdi handling Jan Kara
2017-03-09 10:16 ` [PATCH 1/4] block: Allow bdi re-registration Jan Kara
2017-03-09 16:39 ` Tejun Heo
2017-03-09 10:16 ` [PATCH 2/4] bdi: Fix use-after-free in wb_congested_put() Jan Kara
2017-03-09 10:16 ` [PATCH 3/4] block: Make del_gendisk() safer for disks without queues Jan Kara
2017-03-09 10:16 ` [PATCH 4/4] Revert "scsi, block: fix duplicate bdi name registration crashes" Jan Kara
2017-03-09 16:41 ` Jens Axboe [this message]
2017-03-10 10:22 ` [PATCH 0/4 v2] block: Fixes for bdi handling Jan Kara
2017-03-11 22:27 ` 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=7177cebf-8a9b-10d4-e991-5e43f4303ffc@kernel.dk \
--to=axboe@kernel.dk \
--cc=arthur.marsh@internode.on.net \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osandov@osandov.com \
--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 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.