From: syzbot <syzbot+b904a1de3ec43711eba5@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dvyukov@google.com,
fgheet255t@gmail.com, fmdefrancesco@gmail.com,
jordy@jordyzomer.github.io, jordy@pwning.systems,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, rppt@kernel.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
willy@infradead.org
Subject: Re: [syzbot] WARNING: refcount bug in sys_memfd_secret
Date: Wed, 24 Nov 2021 05:47:06 -0800 [thread overview]
Message-ID: <000000000000f1ea7c05d189175f@google.com> (raw)
In-Reply-To: <00000000000062d0fc05cef24c57@google.com>
syzbot suspects this issue was fixed by commit:
commit 87066fdd2e30fe9dd531125d95257c118a74617e
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sun Oct 24 19:48:33 2021 +0000
Revert "mm/secretmem: use refcount_t instead of atomic_t"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11cccf06b00000
start commit: 9c0c4d24ac00 Merge tag 'block-5.15-2021-10-22' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=be398dd7862f4b36
dashboard link: https://syzkaller.appspot.com/bug?extid=b904a1de3ec43711eba5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=130cabdcb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175b91acb00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Revert "mm/secretmem: use refcount_t instead of atomic_t"
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-11-24 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 15:02 [syzbot] WARNING: refcount bug in sys_memfd_secret syzbot
2021-10-22 15:07 ` Dmitry Vyukov
2021-10-22 16:25 ` Jordy Zomer
2021-10-22 16:29 ` Dmitry Vyukov
2021-10-22 16:39 ` Jordy Zomer
2021-10-23 15:27 ` Mike Rapoport
2021-10-23 17:03 ` Kees Cook
2021-10-23 22:46 ` Matthew Wilcox
2021-10-24 5:37 ` Mike Rapoport
2021-10-24 7:07 ` Dmitry Vyukov
2021-10-24 10:57 ` Matthew Wilcox
2021-10-24 15:31 ` Mike Rapoport
2021-10-23 12:02 ` syzbot
2021-10-23 22:31 ` syzbot
2021-11-24 13:47 ` syzbot [this message]
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=000000000000f1ea7c05d189175f@google.com \
--to=syzbot+b904a1de3ec43711eba5@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=fgheet255t@gmail.com \
--cc=fmdefrancesco@gmail.com \
--cc=jordy@jordyzomer.github.io \
--cc=jordy@pwning.systems \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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.