2019-12-01 07:58:43

by syzbot

[permalink] [raw]
Subject: Re: INFO: task hung in aead_recvmsg

syzbot has bisected this bug to:

commit 0c1e16cd1ec41987cc6671a2bff46ac958c41eb5
Author: Stephan Mueller <[email protected]>
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=56c7151cad94eec37c521f0e47d2eee53f9361c4
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


2019-12-01 17:59:29

by Stephan Müller

[permalink] [raw]
Subject: Re: INFO: task hung in aead_recvmsg

Am Sonntag, 1. Dezember 2019, 08:58:00 CET schrieb syzbot:

Hi,

> syzbot has bisected this bug to:
>
> commit 0c1e16cd1ec41987cc6671a2bff46ac958c41eb5
> Author: Stephan Mueller <[email protected]>
> 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!

Ciao
Stephan


2019-12-01 19:25:29

by Eric Biggers

[permalink] [raw]
Subject: Re: INFO: task hung in aead_recvmsg

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 <[email protected]>
> > 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