From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Wei Fang <fangwei1@huawei.com>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Rabin Vincent <rabinv@axis.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] block: protect iterate_bdevs() against concurrent close
Date: Thu, 1 Dec 2016 02:16:01 -0800 [thread overview]
Message-ID: <20161201101601.GC13993@infradead.org> (raw)
In-Reply-To: <1480580308-15342-1-git-send-email-jack@suse.cz>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2016-12-01 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 8:18 [PATCH] block: protect iterate_bdevs() against concurrent close Jan Kara
2016-12-01 10:16 ` Christoph Hellwig [this message]
2016-12-01 15:27 ` Jens Axboe
2017-01-06 0:03 ` Dan Williams
2017-01-06 0:19 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2016-03-10 12:26 Rabin Vincent
2016-03-10 17:37 ` Jan Kara
2016-03-14 17:42 ` Rabin Vincent
2016-03-15 8:23 ` Jan Kara
2016-03-15 7:51 ` Christoph Hellwig
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=20161201101601.GC13993@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=fangwei1@huawei.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=rabinv@axis.com \
--cc=stable@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 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.