From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Eric Biggers <ebiggers@kernel.org>,
Boris Pismenny <borisp@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
Dave Watson <davejwatson@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
davem@davemloft.net, glider@google.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
syzbot <syzbot+9e3b178624a8a2f8fa28@syzkaller.appspotmail.com>
Subject: Re: [net/tls] Re: KMSAN: uninit-value in aes_encrypt (2)
Date: Fri, 25 Oct 2019 09:37:45 -0700 [thread overview]
Message-ID: <20191025093745.29dcb185@cakuba.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20191025142924.7pgxabkbsbvpgygl@gondor.apana.org.au>
On Fri, 25 Oct 2019 22:29:25 +0800, Herbert Xu wrote:
> On Thu, Oct 24, 2019 at 10:45:37AM -0700, Jakub Kicinski wrote:
> >
> > Oh, thanks for the CC, I don't see any of these in my inbox. We have
> > 6 TLS maintainers, the 3 that were CCed on the thread above don't
> > participate much :(
>
> Can you please ensure that all the maintainers are listed in the
> MAINTAINERS file so people can cc them when needed?
Yes, to be clear we are all listed. Coincidentally we're listed in
order of addition, which turns out to be reverse to the amount of
caring.. And in the threads above it seems someone decided to only
CC first few (i.e. the oldest, i.e. the least caring).
I'll send a patch to remove Dave Watson at least. He's FB email address
is dead, I've been trying to get in touch with him for 2 months with no
luck..
next prev parent reply other threads:[~2019-10-25 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 17:02 KMSAN: uninit-value in aes_encrypt (2) syzbot
2019-10-24 17:23 ` [net/tls] " Eric Biggers
2019-10-24 17:45 ` Jakub Kicinski
2019-10-25 14:29 ` Herbert Xu
2019-10-25 16:37 ` Jakub Kicinski [this message]
2019-10-30 16:08 ` Jakub Kicinski
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=20191025093745.29dcb185@cakuba.hsd1.ca.comcast.net \
--to=jakub.kicinski@netronome.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=glider@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=john.fastabend@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9e3b178624a8a2f8fa28@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;
as well as URLs for NNTP newsgroup(s).