[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190430031144.GG23075@ZenIV.linux.org.uk>
Date: Tue, 30 Apr 2019 04:11:44 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Jan Kara <jack@...e.cz>
Cc: syzbot <syzbot+10007d66ca02b08f0e60@...kaller.appspotmail.com>,
axboe@...nel.dk, dvyukov@...gle.com, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, penguin-kernel@...ove.sakura.ne.jp,
syzkaller-bugs@...glegroups.com
Subject: Re: INFO: task hung in __get_super
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?
Powered by blists - more mailing lists