From: syzbot <syzbot+73a4f2b28371d5526901@syzkaller.appspotmail.com>
To: davem@davemloft.net, fw@strlen.de, hoang.h.le@dektech.com.au,
jmaloy@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
mathew.j.martineau@linux.intel.com, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tadeusz.struk@linaro.org,
tipc-discussion@lists.sourceforge.net, yajun.deng@linux.dev,
ying.xue@windriver.com
Subject: Re: [syzbot] BUG: sleeping function called from invalid context in tipc_crypto_start
Date: Wed, 19 Jan 2022 09:33:12 -0800 [thread overview]
Message-ID: <000000000000b5085105d5f2c7ab@google.com> (raw)
In-Reply-To: <000000000000c5c09805d313d03e@google.com>
syzbot suspects this issue was fixed by commit:
commit f845fe5819efc4111c456c102f15db6d9ed3406e
Author: Hoang Le <hoang.h.le@dektech.com.au>
Date: Fri Dec 17 03:00:59 2021 +0000
Revert "tipc: use consistent GFP flags"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b09d88700000
start commit: 28a2686c185e selftests: Fix IPv6 address bind tests
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=221ffc09e39ebbd1
dashboard link: https://syzkaller.appspot.com/bug?extid=73a4f2b28371d5526901
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1066ce9db00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1398fc6db00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Revert "tipc: use consistent GFP flags"
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-01-19 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 4:42 [syzbot] BUG: sleeping function called from invalid context in tipc_crypto_start syzbot
2022-01-19 17:33 ` syzbot [this message]
2022-01-20 12:47 ` Marco Elver
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=000000000000b5085105d5f2c7ab@google.com \
--to=syzbot+73a4f2b28371d5526901@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=hoang.h.le@dektech.com.au \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tadeusz.struk@linaro.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=yajun.deng@linux.dev \
--cc=ying.xue@windriver.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.