From: "Stephan Müller" <smueller@chronox.de>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+9c251bdd09f83b92ba95@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: [PATCH] AF_ALG: register completely initialized request in list
Date: Thu, 05 Jul 2018 09:49:41 +0200 [thread overview]
Message-ID: <3179058.YavDkrnvkQ@positron.chronox.de> (raw)
In-Reply-To: <20180704233757.GK725@sol.localdomain>
Am Donnerstag, 5. Juli 2018, 01:37:57 CEST schrieb Eric Biggers:
Hi Eric,
> On Mon, Apr 09, 2018 at 09:54:12AM +0200, Stephan Mueller wrote:
> > Am Montag, 9. April 2018, 09:51:13 CEST schrieb Dmitry Vyukov:
> >
> > Hi Dmitry,
> >
> > > You can ask syzbot to test by replying to its report email with a test
> > > command, see:
> > > https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communica
> > > tion -with-syzbot
> > >
> > > Note that all testing of KMSAN bugs needs to go to KMSAN tree, for
> > > details
> > > see:
> > > https://github.com/google/syzkaller/blob/master/docs/syzbot.md#kmsan-bug
> > > s
> >
> > Thank you. I will resend the patch later today with the proper tags.
> >
> > Ciao
> > Stephan
>
> Hi Stephan, it seems you never sent your patch out.
Thank you for pointing this one out. At the time, I was searching for how I
can refer to the syzbot KMSAN branch that was used to produce the bug report.
I only see guidance on how to point to the Linux kernel tree.
Do you have a hint how to point to a different syzbot tree?
Ciao
Stephan
next prev parent reply other threads:[~2018-07-05 7:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:07 KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-04-08 17:57 ` [PATCH] AF_ALG: register completely initialized request in list Stephan Müller
2018-04-09 7:51 ` Dmitry Vyukov
2018-04-09 7:54 ` Stephan Mueller
2018-07-04 23:37 ` Eric Biggers
2018-07-05 7:49 ` Stephan Müller [this message]
2018-07-05 8:43 ` Dmitry Vyukov
2018-07-05 15:58 ` [PATCH v2] AF_ALG: Initialize sg_num_bytes in error code path Stephan Müller
2018-07-05 17:02 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-05 18:45 ` Stephan Müller
2018-07-06 7:38 ` Dmitry Vyukov
2018-07-06 7:41 ` Stephan Mueller
2018-07-06 7:44 ` Dmitry Vyukov
2018-07-06 7:50 ` [PATCH v3] AF_ALG: Initialize sg_num_bytes in error code path Stephan Müller
2018-07-06 7:58 ` Dmitry Vyukov
2018-07-06 8:09 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-06 8:19 ` Dmitry Vyukov
2018-07-06 15:30 ` Dmitry Vyukov
2018-07-06 15:55 ` syzbot
2018-07-06 16:27 ` Stephan Mueller
2018-07-06 21:57 ` [PATCH v3] AF_ALG: Initialize sg_num_bytes in error code path Eric Biggers
2018-07-07 18:41 ` [PATCH v4] " Stephan Müller
2018-07-07 19:01 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-13 10:34 ` [PATCH v4] AF_ALG: Initialize sg_num_bytes in error code path Herbert Xu
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=3179058.YavDkrnvkQ@positron.chronox.de \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9c251bdd09f83b92ba95@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
all inboxes | Powered by JetHome®