From: Al Viro <viro@zeniv.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: syzbot <syzbot+10007d66ca02b08f0e60@syzkaller.appspotmail.com>,
axboe@kernel.dk, dvyukov@google.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in __get_super
Date: Tue, 30 Apr 2019 04:11:44 +0100 [thread overview]
Message-ID: <20190430031144.GG23075@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190430025501.GB6740@quack2.suse.cz>
On Tue, Apr 30, 2019 at 04:55:01AM +0200, Jan Kara wrote:
> Yeah, you're right. And if we push the patch a bit further to not take
> loop_ctl_mutex for invalid ioctl number, that would fix the problem. I
> can send a fix.
Huh? We don't take it until in lo_simple_ioctl(), and that patch doesn't
get to its call on invalid ioctl numbers. What am I missing here?
next prev parent reply other threads:[~2019-04-30 3:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 17:08 INFO: task hung in __get_super syzbot
2018-06-19 11:44 ` Tetsuo Handa
2018-06-19 11:53 ` Dmitry Vyukov
2018-06-19 14:10 ` Tetsuo Handa
2018-06-19 14:15 ` Dmitry Vyukov
2018-06-20 1:15 ` Tetsuo Handa
2019-04-28 18:14 ` syzbot
2019-04-28 18:51 ` Al Viro
2019-04-29 1:38 ` Tetsuo Handa
2019-04-29 5:30 ` Dmitry Vyukov
2019-04-30 2:55 ` Jan Kara
2019-04-30 3:11 ` Al Viro [this message]
2019-04-30 13:07 ` Jan Kara
2019-04-30 13:18 ` Al Viro
2019-04-30 15:07 ` Jan Kara
2019-04-30 15:34 ` Tetsuo Handa
2019-05-03 10:29 ` Tetsuo Handa
2019-05-14 5:15 ` Tetsuo Handa
2019-05-15 1:02 ` Tetsuo Handa
2019-05-15 10:21 ` Jan Kara
2019-05-15 11:32 ` Tetsuo Handa
2019-05-15 13:07 ` Jan Kara
2019-05-16 11:48 ` Jan Kara
2019-05-16 12:17 ` Tetsuo Handa
2019-05-16 12:32 ` Jan Kara
2019-05-16 12:50 ` Tetsuo Handa
2019-05-16 12:33 ` syzbot
2019-05-15 11:59 ` syzbot
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=20190430031144.GG23075@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=axboe@kernel.dk \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzbot+10007d66ca02b08f0e60@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 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.