From: Greg KH <gregkh@linuxfoundation.org>
To: syzbot
<bot+1fdad4e2731bf0c1bc19953ccc5061237ec92783@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in sysfs_warn_dup
Date: Tue, 19 Dec 2017 10:01:21 +0100 [thread overview]
Message-ID: <20171219090121.GA10221@kroah.com> (raw)
In-Reply-To: <001a11c14bc837f9760560a03d51@google.com>
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
next parent reply other threads:[~2017-12-19 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a11c14bc837f9760560a03d51@google.com>
2017-12-19 9:01 ` Greg KH [this message]
[not found] ` <CACT4Y+ZggKsEjCRZsFPW5-7_ByBcz4G0uRdieLL==r4mLQjhFA@mail.gmail.com>
2017-12-19 9:06 ` WARNING in sysfs_warn_dup Dmitry Vyukov
2018-01-22 13:47 ` Dmitry Vyukov
2018-01-22 13:47 ` Dmitry Vyukov
2018-01-22 14:00 ` Greg KH
2018-01-22 14:30 ` Dmitry Vyukov
2018-01-22 14:30 ` Dmitry Vyukov
2018-01-22 14:45 ` Greg KH
2018-01-22 15:04 ` Dmitry Vyukov
2018-01-22 15:04 ` Dmitry Vyukov
2018-01-22 15:04 ` Dmitry Vyukov
2018-01-22 14:57 ` [PATCH] sysfs: turn WARN() into pr_warn() Greg KH
2018-01-22 15:04 ` Dmitry Vyukov
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=20171219090121.GA10221@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bot+1fdad4e2731bf0c1bc19953ccc5061237ec92783@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.