Re: WARNING: suspicious RCU usage (3)

2017-12-01 Thread Dmitry Vyukov
On Thu, Nov 30, 2017 at 9:04 AM, Dmitry Vyukov wrote: > On Thu, Nov 30, 2017 at 1:47 AM, Eric Biggers wrote: >> On Tue, Nov 28, 2017 at 09:06:06PM -0800, Eric Biggers wrote: >>> On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote: >>> > >>> > It looks like blkcipher_walk_done() passed a

Re: WARNING: suspicious RCU usage (3)

2017-11-30 Thread Dmitry Vyukov
On Thu, Nov 30, 2017 at 1:47 AM, Eric Biggers wrote: > On Tue, Nov 28, 2017 at 09:06:06PM -0800, Eric Biggers wrote: >> 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 unin

Re: WARNING: suspicious RCU usage (3)

2017-11-29 Thread Eric Biggers
On Tue, Nov 28, 2017 at 09:06:06PM -0800, Eric Biggers wrote: > 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

Re: WARNING: suspicious RCU usage (3)

2017-11-29 Thread Paul E. McKenney
On Wed, Nov 29, 2017 at 07:25:32AM +0100, Dmitry Vyukov wrote: > On Tue, Nov 28, 2017 at 11:30 PM, Paul E. McKenney > wrote: > > On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote: > >> On Tue, 28 Nov 2017 12:45:01 -0800 syzbot > >> > >> wrote: > >> > >> > Hello, > >> > > >> > syzkal

Re: WARNING: suspicious RCU usage (3)

2017-11-28 Thread Dmitry Vyukov
On Tue, Nov 28, 2017 at 11:30 PM, Paul E. McKenney wrote: > On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote: >> On Tue, 28 Nov 2017 12:45:01 -0800 syzbot >> >> wrote: >> >> > Hello, >> > >> > syzkaller hit the following crash on >> > b0a84f19a5161418d4360cd57603e94ed489915e >> > g

Re: WARNING: suspicious RCU usage (3)

2017-11-28 Thread Eric Biggers
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:

Re: WARNING: suspicious RCU usage (3)

2017-11-28 Thread Paul E. McKenney
On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote: > On Tue, 28 Nov 2017 12:45:01 -0800 syzbot > > wrote: > > > Hello, > > > > syzkaller hit the following crash on > > b0a84f19a5161418d4360cd57603e94ed489915e > > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/m

Re: WARNING: suspicious RCU usage (3)

2017-11-28 Thread Andrew Morton
On Tue, 28 Nov 2017 12:45:01 -0800 syzbot wrote: > Hello, > > syzkaller hit the following crash on > b0a84f19a5161418d4360cd57603e94ed489915e > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console out