From: syzbot <syzbot+b9c67110e04430822b08@syzkaller.appspotmail.com>
To: daeho43@gmail.com, daehojeong@google.com, jaegeuk@kernel.org,
joneslee@google.com, kernel-team@android.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, nogikh@google.com,
syzkaller-android-bugs@googlegroups.com,
tudor.ambarus@linaro.org
Subject: Re: [f2fs-dev] [Android 5.15] BUG: scheduling while atomic in f2fs_register_inmem_page
Date: Mon, 25 Dec 2023 14:43:04 -0800 [thread overview]
Message-ID: <000000000000f5d50e060d5d493b@google.com> (raw)
In-Reply-To: <00000000000052dcf505f6fc93af@google.com>
syzbot suspects this issue was fixed by commit:
commit 76ca4a07659a31cc62977664bcf638d6a24af068
Author: Daeho Jeong <daehojeong@google.com>
Date: Thu Apr 28 18:18:09 2022 +0000
BACKPORT: f2fs: change the current atomic write way
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11287ba5e80000
start commit: 61cfd264993d Revert "ipv4/fib: send notify when delete sou..
git tree: android13-5.15-lts
kernel config: https://syzkaller.appspot.com/x/.config?x=86febd5cba631f80
dashboard link: https://syzkaller.appspot.com/bug?extid=b9c67110e04430822b08
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135fe388e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171ba588e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: BACKPORT: f2fs: change the current atomic write way
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
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+b9c67110e04430822b08@syzkaller.appspotmail.com>
To: daeho43@gmail.com, daehojeong@google.com, jaegeuk@kernel.org,
joneslee@google.com, kernel-team@android.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, nogikh@google.com,
syzkaller-android-bugs@googlegroups.com,
tudor.ambarus@linaro.org
Subject: Re: [Android 5.15] BUG: scheduling while atomic in f2fs_register_inmem_page
Date: Mon, 25 Dec 2023 14:43:04 -0800 [thread overview]
Message-ID: <000000000000f5d50e060d5d493b@google.com> (raw)
In-Reply-To: <00000000000052dcf505f6fc93af@google.com>
syzbot suspects this issue was fixed by commit:
commit 76ca4a07659a31cc62977664bcf638d6a24af068
Author: Daeho Jeong <daehojeong@google.com>
Date: Thu Apr 28 18:18:09 2022 +0000
BACKPORT: f2fs: change the current atomic write way
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11287ba5e80000
start commit: 61cfd264993d Revert "ipv4/fib: send notify when delete sou..
git tree: android13-5.15-lts
kernel config: https://syzkaller.appspot.com/x/.config?x=86febd5cba631f80
dashboard link: https://syzkaller.appspot.com/bug?extid=b9c67110e04430822b08
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=135fe388e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171ba588e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: BACKPORT: f2fs: change the current atomic write way
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2023-12-25 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000052dcf505f6fc93af@google.com>
2023-12-25 22:43 ` syzbot [this message]
2023-12-25 22:43 ` [Android 5.15] BUG: scheduling while atomic in f2fs_register_inmem_page syzbot
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=000000000000f5d50e060d5d493b@google.com \
--to=syzbot+b9c67110e04430822b08@syzkaller.appspotmail.com \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=joneslee@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nogikh@google.com \
--cc=syzkaller-android-bugs@googlegroups.com \
--cc=tudor.ambarus@linaro.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.