From: Eric Biggers <ebiggers3@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot
<bot+73a7bec1bc0f4fc0512a246334081f8c671762a8@syzkaller.appspotmail.com>,
cl@linux.com, iamjoonsoo.kim@lge.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
penberg@kernel.org, rientjes@google.com,
syzkaller-bugs@googlegroups.com,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: WARNING: suspicious RCU usage (3)
Date: Tue, 28 Nov 2017 21:06:06 -0800 [thread overview]
Message-ID: <20171129050606.GF24001@zzz.localdomain> (raw)
In-Reply-To: <20171128133026.cf03471c99d7a0c827c5a21c@linux-foundation.org>
On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote:
>
> It looks like blkcipher_walk_done() passed a bad address to kfree().
>
Indeed, it's freeing uninitialized memory because the Salsa20 algorithms are
using the blkcipher_walk API incorrectly. I've sent a patch to fix it:
"crypto: salsa20 - fix blkcipher_walk API usage"
I am not sure why the bug reports show up as "suspicious RCU usage", though.
There were also a few other syzbot reports of this same underlying bug; I marked
them as duplicates of this one.
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-29 5:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 20:45 WARNING: suspicious RCU usage (3) syzbot
2017-11-28 21:30 ` Andrew Morton
2017-11-28 22:30 ` Paul E. McKenney
2017-11-29 6:25 ` Dmitry Vyukov
2017-11-29 20:50 ` Paul E. McKenney
2017-11-29 5:06 ` Eric Biggers [this message]
2017-11-30 0:47 ` Eric Biggers
2017-11-30 8:04 ` Dmitry Vyukov
2017-12-01 8:28 ` Dmitry Vyukov
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=20171129050606.GF24001@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bot+73a7bec1bc0f4fc0512a246334081f8c671762a8@syzkaller.appspotmail.com \
--cc=cl@linux.com \
--cc=herbert@gondor.apana.org.au \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@us.ibm.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=syzkaller-bugs@googlegroups.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 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).