Linux cryptographic layer development
 help / color / mirror / Atom feed
From: syzbot <bot+e5e6fab2d4dc3d9877ac240fed364027bb960ad0@syzkaller.appspotmail.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: davem@davemloft.net, dvyukov@google.com,
	herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, smueller@chronox.de,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in crypto_aead_free_instance
Date: Wed, 20 Dec 2017 01:55:30 -0800	[thread overview]
Message-ID: <001a113f861e70dc700560c295dc@google.com> (raw)
In-Reply-To: <18467907.EfXNf1iGip@tauon.chronox.de>

> Am Mittwoch, 20. Dezember 2017, 10:50:10 CET schrieb Dmitry Vyukov:

> Hi Dmitry,

>> On Wed, Dec 20, 2017 at 10:29 AM, Stephan Mueller <smueller@chronox.de>
> wrote:
>> > Am Mittwoch, 20. Dezember 2017, 10:19:43 CET schrieb Dmitry Vyukov:
>> >
>> > Hi Dmitry,
>> >
>> >> > This issue vanishes after applying the patch "[PATCH v2] crypto:  
>> AF_ALG
>> >> > -
>> >> > limit mask and type".
>> >>
>> >> Hi Stephan,
>> >>
>> >> syzbot does not understand arbitrary English prose, it only  
>> understands
>> >
>> > this:
>> >> > Once a fix for this bug is merged into any tree, reply to this email
>> >> > with:
>> >> > #syz fix: exact-commit-title
>> >>
>> >> Let's tell it about the fix:
>> >>
>> >> #syz fix: crypto: AF_ALG - limit mask and type
>> >
>> > I have seen that this is the approach, but the fix is not yet in the  
>> tree.
>> > I just want to let folks know that there is a patch.

>> Ah, ok, sorry. It's just difficult to tell when there is a reason to
>> not provide the tag right now, or when people are don't know about
>> them or ignore.
>> If the patch is merged with this title, then there is nothing else to
>> do. If it's merged under a different title, a new "#syz fix:" tag will
>> override the old one.

> Maybe you can teach the syzcaller that there is a proposed fix? E.g.

> #syz proposed: commit-title

unknown command "proposed:"



> Ciao
> Stephan

> --
> You received this message because you are subscribed to the Google  
> Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit  
> https://groups.google.com/d/msgid/syzkaller-bugs/18467907.EfXNf1iGip%40tauon.chronox.de.
> For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2017-12-20  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20  7:48 KASAN: use-after-free Read in crypto_aead_free_instance syzbot
2017-12-20  9:17 ` Stephan Müller
2017-12-20  9:19   ` Dmitry Vyukov
2017-12-20  9:29     ` Stephan Mueller
2017-12-20  9:50       ` Dmitry Vyukov
2017-12-20  9:55         ` Stephan Mueller
2017-12-20  9:55           ` syzbot
2017-12-20  9:55           ` syzbot [this message]
2017-12-20 10:15           ` Dmitry Vyukov
2017-12-20 11:49             ` Stephan Mueller
2017-12-20 11:59               ` Dmitry Vyukov
2017-12-20 22:37 ` Eric Biggers

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=001a113f861e70dc700560c295dc@google.com \
    --to=bot+e5e6fab2d4dc3d9877ac240fed364027bb960ad0@syzkaller.appspotmail.com \
    --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=smueller@chronox.de \
    --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