[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20171219090121.GA10221@kroah.com>
Date: Tue, 19 Dec 2017 10:01:21 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: syzbot
<bot+1fdad4e2731bf0c1bc19953ccc5061237ec92783@...kaller.appspotmail.com>
Cc: linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: WARNING in sysfs_warn_dup
On Mon, Dec 18, 2017 at 08:57:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 6084b576dca2e898f5c101baef151f7bfdbb606d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
>
> Unfortunately, I don't have any reproducer for this bug yet.
>
>
> netlink: 9 bytes leftover after parsing attributes in process
> `syz-executor3'.
> sg_write: data in/out 822404280/197 bytes for SCSI command 0x12-- guessing
> data in;
> program syz-executor0 not setting count and/or reply_len properly
> sg_write: data in/out 262364/161 bytes for SCSI command 0xff-- guessing data
> in;
> program syz-executor0 not setting count and/or reply_len properly
> WARNING: CPU: 1 PID: 22282 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x60/0x80
> fs/sysfs/dir.c:30
> Kernel panic - not syncing: panic_on_warn set ...
Looks like a networking issue, it tried to create two sysfs directories
with the same name, which isn't a sysfs bug :)
thanks,
greg k-h
Powered by blists - more mailing lists