From: Stephan Mueller <smueller@chronox.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot
<bot+e5e6fab2d4dc3d9877ac240fed364027bb960ad0@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in crypto_aead_free_instance
Date: Wed, 20 Dec 2017 12:49:47 +0100 [thread overview]
Message-ID: <12415329.MInO136rYd@tauon.chronox.de> (raw)
In-Reply-To: <CACT4Y+bg6GjHbLpSkB6joS_dgu3ZYH=mJXHJ8AnuWiPVokhBdA@mail.gmail.com>
Am Mittwoch, 20. Dezember 2017, 11:15:38 CET schrieb Dmitry Vyukov:
Hi Dmitry,
>
> What will be its meaning? How will it differ from fix?
Maybe a short clarification would help: what is the meaning of the syz fix
marker? Depending on this answer, all that I am thinking of is to mark bug
reports for which there are fixes actively discussed, but yet not integrated.
Thus, such marker should only help others to point them to active discussions
instead of them trying to find fixes alone.
Ciao
Stephan
next prev parent reply other threads:[~2017-12-20 11:49 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
2017-12-20 10:15 ` Dmitry Vyukov
2017-12-20 11:49 ` Stephan Mueller [this message]
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=12415329.MInO136rYd@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=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=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