mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: "Stephan Müller" <smueller@chronox.de>
Cc: syzbot 
	<syzbot+56c7151cad94eec37c521f0e47d2eee53f9361c4@syzkaller.appspotmail.com>,
	davem@davemloft.net, dvyukov@google.com,
	herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	peterz@infradead.org, steffen.klassert@secunet.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in aead_recvmsg
Date: Sun, 1 Dec 2019 11:22:22 -0800	[thread overview]
Message-ID: <20191201192222.GA1186@sol.localdomain> (raw)
In-Reply-To: <2842590.QEqkPaeV8v@positron.chronox.de>

On Sun, Dec 01, 2019 at 06:58:17PM +0100, Stephan Müller wrote:
> Am Sonntag, 1. Dezember 2019, 08:58:00 CET schrieb syzbot:
> 
> Hi,
> 
> > syzbot has bisected this bug to:
> > 
> > commit 0c1e16cd1ec41987cc6671a2bff46ac958c41eb5
> > Author: Stephan Mueller <smueller@chronox.de>
> > Date:   Mon Dec 5 14:26:19 2016 +0000
> > 
> >      crypto: algif_aead - fix AEAD tag memory handling
> > 
> > bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12d6d0a6e00000
> > start commit:   618d919c Merge tag 'libnvdimm-fixes-5.1-rc6' of git://git...
> > git tree:       upstream
> > final crash:    https://syzkaller.appspot.com/x/report.txt?x=11d6d0a6e00000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=16d6d0a6e00000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=856fc6d0fbbeede9
> > dashboard link:
> > https://syzkaller.appspot.com/bug?extid=56c7151cad94eec37c521f0e47d2eee53f93
> > 61c4 syz repro:     
> > https://syzkaller.appspot.com/x/repro.syz?x=11ef592d200000 C reproducer:  
> > https://syzkaller.appspot.com/x/repro.c?x=16b865fd200000
> > 
> > Reported-by:
> > syzbot+56c7151cad94eec37c521f0e47d2eee53f9361c4@syzkaller.appspotmail.com
> > Fixes: 0c1e16cd1ec4 ("crypto: algif_aead - fix AEAD tag memory handling")
> > 
> > For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 
> This issue seems to be triggered when using pcrypt. Pcrypt received a number 
> of fixes recently.
> 
> Did the test include all of those fixes?
> 
> Thanks a lot for the testing!
> 

No, the pcrypt fixes haven't been applied yet.  One of Herbert's patches has:

	Reported-by: syzbot+56c7151cad94eec37c521f0e47d2eee53f9361c4@syzkaller.appspotmail.com

... so syzbot will close this bug report once this patch is applied and reaches
upstream or linux-next.  It's just a coincidence that syzbot happened to report
a bisection result now.

- Eric

      reply	other threads:[~2019-12-01 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001a1140b8307b0439055ffc7872@google.com>
2017-12-12 16:46 ` Dmitry Vyukov
2017-12-23 20:29   ` Eric Biggers
2017-12-30  8:37     ` Steffen Klassert
2018-01-05 21:35       ` Eric Biggers
2018-07-21 12:37 ` syzbot
2019-12-01  7:58 ` syzbot
2019-12-01 17:58   ` Stephan Müller
2019-12-01 19:22     ` Eric Biggers [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=20191201192222.GA1186@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=smueller@chronox.de \
    --cc=steffen.klassert@secunet.com \
    --cc=syzbot+56c7151cad94eec37c521f0e47d2eee53f9361c4@syzkaller.appspotmail.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

Powered by JetHome