From: syzbot <syzbot+8ab2d0f39fb79fe6ca40@syzkaller.appspotmail.com>
To: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yuchao0@huawei.com
Subject: Re: INFO: task syz-executor can't die for more than 143 seconds.
Date: Wed, 12 Jun 2019 19:53:00 -0700 [thread overview]
Message-ID: <000000000000c0103a058b2ba0ec@google.com> (raw)
In-Reply-To: <000000000000a861f6058b2699e0@google.com>
syzbot has bisected this bug to:
commit 4ddc1b28aac57a90c6426d55e0dea3c1b5eb4782
Author: Chao Yu <yuchao0@huawei.com>
Date: Wed Jul 25 23:19:48 2018 +0000
f2fs: fix to restrict mount condition when without CONFIG_QUOTA
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142f4e49a00000
start commit: 81a72c79 Add linux-next specific files for 20190612
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=122f4e49a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8aa46bbce201b8b6
dashboard link: https://syzkaller.appspot.com/bug?extid=8ab2d0f39fb79fe6ca40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1250ae3ea00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1568557aa00000
Reported-by: syzbot+8ab2d0f39fb79fe6ca40@syzkaller.appspotmail.com
Fixes: 4ddc1b28aac5 ("f2fs: fix to restrict mount condition when without
CONFIG_QUOTA")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+8ab2d0f39fb79fe6ca40@syzkaller.appspotmail.com>
To: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
yuchao0@huawei.com
Subject: Re: [f2fs-dev] INFO: task syz-executor can't die for more than 143 seconds.
Date: Wed, 12 Jun 2019 19:53:00 -0700 [thread overview]
Message-ID: <000000000000c0103a058b2ba0ec@google.com> (raw)
Message-ID: <20190613025300.QfX8DWbwhTZm6eNiOFSiAJ-UxMHOnyNUusbtt73dJOM@z> (raw)
In-Reply-To: <000000000000a861f6058b2699e0@google.com>
syzbot has bisected this bug to:
commit 4ddc1b28aac57a90c6426d55e0dea3c1b5eb4782
Author: Chao Yu <yuchao0@huawei.com>
Date: Wed Jul 25 23:19:48 2018 +0000
f2fs: fix to restrict mount condition when without CONFIG_QUOTA
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142f4e49a00000
start commit: 81a72c79 Add linux-next specific files for 20190612
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=122f4e49a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8aa46bbce201b8b6
dashboard link: https://syzkaller.appspot.com/bug?extid=8ab2d0f39fb79fe6ca40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1250ae3ea00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1568557aa00000
Reported-by: syzbot+8ab2d0f39fb79fe6ca40@syzkaller.appspotmail.com
Fixes: 4ddc1b28aac5 ("f2fs: fix to restrict mount condition when without
CONFIG_QUOTA")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-06-13 2:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 20:53 INFO: task syz-executor can't die for more than 143 seconds syzbot
2019-06-13 2:53 ` syzbot [this message]
2019-06-13 2:53 ` [f2fs-dev] " syzbot
2019-06-14 10:16 ` [PATCH] kexec: Bail out upon SIGKILL when allocating memory Tetsuo Handa
2019-07-01 10:52 ` Tetsuo Handa
2019-07-23 13:22 ` Tetsuo Handa
2019-07-24 2:54 ` Eric Biggers
2019-07-24 3:09 ` Tetsuo Handa
2019-06-21 9:58 ` INFO: task syz-executor can't die for more than 143 seconds Tetsuo Handa
2019-07-01 10:55 ` [PATCH] staging: android: ion: Bail out upon SIGKILL when allocating memory Tetsuo Handa
2019-07-01 11:36 ` Laura Abbott
2019-07-01 14:02 ` Sumit Semwal
2019-07-01 21:02 ` Tetsuo Handa
2019-07-01 21:21 ` Laura Abbott
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=000000000000c0103a058b2ba0ec@google.com \
--to=syzbot+8ab2d0f39fb79fe6ca40@syzkaller.appspotmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuchao0@huawei.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.