From: Herbert Xu <herbert@gondor.apana.org.au>
To: syzbot <syzbot+4cbd5e3669aee5ac5149@syzkaller.appspotmail.com>
Cc: a.darwish@linutronix.de, davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, peterz@infradead.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com,
will@kernel.org
Subject: Re: possible deadlock in xfrm_policy_lookup_bytype
Date: Thu, 24 Sep 2020 14:25:22 +1000 [thread overview]
Message-ID: <20200924042522.GD9255@gondor.apana.org.au> (raw)
In-Reply-To: <00000000000025fe5805afbc876c@google.com>
#syz dup: inconsistent lock state in xfrm_policy_lookup_inexact_addr
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2020-09-24 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 10:52 possible deadlock in xfrm_policy_lookup_bytype syzbot
2020-09-24 4:25 ` Herbert Xu [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=20200924042522.GD9255@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=a.darwish@linutronix.de \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+4cbd5e3669aee5ac5149@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).