All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com>
To: chao@kernel.org, linux-erofs@lists.ozlabs.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 xiang@kernel.org
Subject: Re: [syzbot] WARNING: kobject bug in erofs_unregister_sysfs
Date: Fri, 18 Mar 2022 11:52:07 -0700	[thread overview]
Message-ID: <000000000000aff2c805da82a426@google.com> (raw)
In-Reply-To: <YjTJRQb9eMXdsHOE@debian>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com

Tested on:

commit:         a1108dcd erofs: rename ctime to mtime
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev
kernel config:  https://syzkaller.appspot.com/x/.config?x=442f8ac61e60a75e
dashboard link: https://syzkaller.appspot.com/bug?extid=f05ba4652c0471416eaf
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2022-03-18 18:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 16:39 [syzbot] WARNING: kobject bug in erofs_unregister_sysfs syzbot
2022-03-18 18:02 ` Gao Xiang
2022-03-18 18:02   ` Gao Xiang
2022-03-18 18:52   ` syzbot [this message]
2022-03-18 22:33 ` syzbot
2022-03-19  2:19   ` Muchun Song
2022-03-19  2:19     ` Muchun Song
2022-03-19  3:45     ` Gao Xiang
2022-03-19  3:45       ` Gao Xiang
2022-03-20  4:19     ` Dongliang Mu
2022-03-20  4:19       ` Dongliang Mu
2022-03-21  6:55       ` Dmitry Vyukov via Linux-erofs
2022-03-21  6:55         ` Dmitry Vyukov
2022-03-23  1:54         ` Gao Xiang
2022-03-23  1:54           ` Gao Xiang

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=000000000000aff2c805da82a426@google.com \
    --to=syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com \
    --cc=chao@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiang@kernel.org \
    /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.