From: Christoph Hellwig <hch@lst.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Christoph Hellwig <hch@lst.de>,
Dan Schatzberg <schatzberg.dan@gmail.com>,
Ming Lei <ming.lei@redhat.com>,
axboe@kernel.dk, linux-block@vger.kernel.org
Subject: Re: [syzbot] possible deadlock in __loop_clr_fd (3)
Date: Mon, 15 Nov 2021 10:58:08 +0100 [thread overview]
Message-ID: <20211115095808.GA32005@lst.de> (raw)
In-Reply-To: <7d851c88-f657-dfd8-34ab-4891ac6388dc@i-love.sakura.ne.jp>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2021-11-15 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 17:00 [syzbot] possible deadlock in __loop_clr_fd (3) syzbot
2021-11-10 22:10 ` Tetsuo Handa
2021-11-11 0:55 ` Dan Schatzberg
2021-11-11 15:14 ` Tetsuo Handa
2021-11-12 6:20 ` Christoph Hellwig
2021-11-12 16:25 ` Tetsuo Handa
2021-11-15 9:58 ` Christoph Hellwig [this message]
2021-11-15 10:20 ` [PATCH v2] loop: don't hold lo_mutex during __loop_clr_fd() Tetsuo Handa
2021-11-24 10:47 ` [PATCH v3] " Tetsuo Handa
2021-11-24 15:35 ` 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=20211115095808.GA32005@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=schatzberg.dan@gmail.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 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).