From: Christoph Hellwig <hch@lst.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Hillf Danton <hdanton@sina.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
linux-block <linux-block@vger.kernel.org>,
Milan Broz <gmazyland@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: sort out the lock order in the loop driver v2
Date: Fri, 27 Aug 2021 17:34:16 +0200 [thread overview]
Message-ID: <20210827153416.GB20687@lst.de> (raw)
In-Reply-To: <67aa49f1-c3d4-205f-fd08-0bc0dbcd3689@i-love.sakura.ne.jp>
On Fri, Aug 27, 2021 at 04:46:42PM +0900, Tetsuo Handa wrote:
> On 2021/08/27 15:40, Christoph Hellwig wrote:
> > On Fri, Aug 27, 2021 at 09:30:12AM +0900, Tetsuo Handa wrote:
> >> Again crashed in 3 seconds. We can't accept this series.
> >
> > Would you gladly point to the reproducer?
> >
>
> You can reach dashboard at https://syzkaller.appspot.com/bug?extid=$hashid where
> $hashid is Reporter's mail address <syzbot+$hashid@syzkaller.appspotmail.com> .
> For this bug report, the dashboard is https://syzkaller.appspot.com/bug?extid=f61766d5763f9e7a118f .
> Then, please find C repro column within the dashboard page. For this bug report, the C reproducer is
> https://syzkaller.appspot.com/text?tag=ReproC&x=13d20adc300000 .
Thank you very much!
next prev parent reply other threads:[~2021-08-27 15:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 13:38 sort out the lock order in the loop driver v2 Christoph Hellwig
2021-08-26 13:38 ` [PATCH 1/8] cryptoloop: fix a sparse annotation Christoph Hellwig
2021-08-26 13:38 ` [PATCH 2/8] loop: remove the unused idx argument to loop_control_get_free Christoph Hellwig
2021-08-26 13:38 ` [PATCH 3/8] loop: remove the ->ioctl method in loop_func_table Christoph Hellwig
2021-08-26 13:38 ` [PATCH 4/8] loop: return void from the ->release " Christoph Hellwig
2021-08-26 13:38 ` [PATCH 5/8] loop: merge the cryptoloop module into the main loop module Christoph Hellwig
2021-08-26 16:31 ` Milan Broz
2021-08-26 16:34 ` Christoph Hellwig
2021-08-26 16:44 ` Milan Broz
2021-08-27 6:45 ` Christoph Hellwig
2021-08-27 11:33 ` Tetsuo Handa
2021-08-27 15:38 ` Christoph Hellwig
2021-08-26 13:38 ` [PATCH 6/8] loop: devirtualize transfer transformations Christoph Hellwig
2021-08-26 13:38 ` [PATCH 7/8] loop: move loop device deletion out of loop_ctl_mutex Christoph Hellwig
2021-08-26 13:38 ` [PATCH 8/8] loop: avoid holding loop_ctl_mutex over add_disk Christoph Hellwig
2021-08-27 0:30 ` sort out the lock order in the loop driver v2 Tetsuo Handa
2021-08-27 6:40 ` Christoph Hellwig
2021-08-27 7:46 ` Tetsuo Handa
2021-08-27 15:34 ` Christoph Hellwig [this message]
[not found] ` <20210827130259.2622-1-hdanton@sina.com>
2021-08-27 14:10 ` Tetsuo Handa
[not found] ` <20210828035114.2762-1-hdanton@sina.com>
2021-08-28 5:17 ` Tetsuo Handa
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=20210827153416.GB20687@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=gmazyland@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tyhicks@linux.microsoft.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).