From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH v1 0/5] treewide cleanup of random integer usage
Date: Thu, 6 Oct 2022 06:58:19 -0600 [thread overview]
Message-ID: <CAHmME9pvW1SF5hfaE796KLmisbX2TK67F3xO6OKV2ZBiqvEeOg@mail.gmail.com> (raw)
In-Reply-To: <202210052310.BF756EBEBE@keescook>
On Thu, Oct 6, 2022 at 12:15 AM Kees Cook <keescook@chromium.org> wrote:
>
> On Wed, Oct 05, 2022 at 11:48:39PM +0200, Jason A. Donenfeld wrote:
> > I've CC'd get_maintainers.pl, which is a pretty big list. Probably some
> > portion of those are going to bounce, too, and everytime you reply to
>
> The real problem is that replies may not reach the vger lists:
>
> Subject: BOUNCE linux-kernel@vger.kernel.org: Header field too long (>8192)
>
> But the originals somehow ended up on lore?
>
> https://lore.kernel.org/lkml/20221005214844.2699-1-Jason@zx2c4.com/
Heh, those aren't quite the originals. Same message IDs, but I did
evil things to get them on there.
v2 coming shortly to rectify this mess.
Jason
prev parent reply other threads:[~2022-10-06 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 21:48 [PATCH v1 0/5] treewide cleanup of random integer usage Jason A. Donenfeld
2022-10-05 21:48 ` [PATCH v1 1/5] treewide: use prandom_u32_max() when possible Jason A. Donenfeld
2022-10-05 21:48 ` [PATCH v1 2/5] treewide: use get_random_{u8,u16}() " Jason A. Donenfeld
2022-10-06 13:37 ` Toke Høiland-Jørgensen
2022-10-05 21:48 ` [PATCH v1 3/5] treewide: use get_random_u32() " Jason A. Donenfeld
[not found] ` <20221006084331.4bdktc2zlvbaszym@quack3>
[not found] ` <Yz7LCyIAHC6l5mG9@zx2c4.com>
2022-10-06 13:01 ` [f2fs-dev] " Andy Shevchenko
2022-10-06 13:07 ` Jason A. Donenfeld
[not found] ` <Yz7OdfKZeGkpZSKb@ziepe.ca>
[not found] ` <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
2022-10-06 13:15 ` Jason Gunthorpe
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:38 ` Toke Høiland-Jørgensen
2022-10-12 19:16 ` Joe Perches
2022-10-12 21:29 ` David Laight
2022-10-13 1:37 ` Joe Perches
2022-10-05 21:48 ` [PATCH v1 4/5] treewide: use get_random_bytes " Jason A. Donenfeld
2022-10-05 21:48 ` [PATCH v1 5/5] prandom: remove unused functions Jason A. Donenfeld
2022-10-06 6:15 ` [PATCH v1 0/5] treewide cleanup of random integer usage Kees Cook
2022-10-06 12:58 ` Jason A. Donenfeld [this message]
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=CAHmME9pvW1SF5hfaE796KLmisbX2TK67F3xO6OKV2ZBiqvEeOg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).