[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221214162117.GC1062210@linux.intel.com>
Date: Wed, 14 Dec 2022 17:21:17 +0100
From: Stanislaw Gruszka <stanislaw.gruszka@...ux.intel.com>
To: Eric Dumazet <edumazet@...gle.com>
Cc: "Jason A. Donenfeld" <Jason@...c4.com>,
Vignesh Raghavendra <vigneshr@...com>,
Peter Zijlstra <peterz@...radead.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Alexei Starovoitov <ast@...nel.org>,
dri-devel@...ts.freedesktop.org, Song Liu <song@...nel.org>,
linux-mtd@...ts.infradead.org, Stanislav Fomichev <sdf@...gle.com>,
"H. Peter Anvin" <hpa@...or.com>,
Hyeonggon Yoo <42.hyeyoo@...il.com>,
Christoph Lameter <cl@...ux.com>,
Daniel Borkmann <daniel@...earbox.net>,
Richard Weinberger <richard@....at>, x86@...nel.org,
John Fastabend <john.fastabend@...il.com>,
Andrii Nakryiko <andrii@...nel.org>, ilay.bahat1@...il.com,
Ingo Molnar <mingo@...hat.com>,
David Rientjes <rientjes@...gle.com>,
Yonghong Song <yhs@...com>, Paolo Abeni <pabeni@...hat.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Petr Mladek <pmladek@...e.com>,
david.keisarschm@...l.huji.ac.il,
Dave Hansen <dave.hansen@...ux.intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
intel-gfx@...ts.freedesktop.org,
Steven Rostedt <rostedt@...dmis.org>,
KP Singh <kpsingh@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Borislav Petkov <bp@...en8.de>, Hannes Reinecke <hare@...e.de>,
Andy Lutomirski <luto@...nel.org>,
Jiri Pirko <jiri@...dia.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
bpf@...r.kernel.org, Vlastimil Babka <vbabka@...e.cz>,
Hao Luo <haoluo@...gle.com>, linux-scsi@...r.kernel.org,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-mm@...ck.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Pekka Enberg <penberg@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
aksecurity@...il.com, Jiri Olsa <jolsa@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 1/5] Renaming weak prng invocations -
prandom_bytes_state, prandom_u32_state
On Wed, Dec 14, 2022 at 04:15:49PM +0100, Eric Dumazet wrote:
> On Wed, Dec 14, 2022 at 1:34 PM Stanislaw Gruszka
> <stanislaw.gruszka@...ux.intel.com> wrote:
> >
> > On Mon, Dec 12, 2022 at 03:35:20PM +0100, Jason A. Donenfeld wrote:
> > > Please CC me on future revisions.
> > >
> > > As of 6.2, the prandom namespace is *only* for predictable randomness.
> > > There's no need to rename anything. So nack on this patch 1/5.
> >
> > It is not obvious (for casual developers like me) that p in prandom
> > stands for predictable. Some renaming would be useful IMHO.
>
> Renaming makes backports more complicated, because stable teams will
> have to 'undo' name changes.
> Stable teams are already overwhelmed by the amount of backports, and
> silly merge conflicts.
Since when backporting problems is valid argument for stop making
changes? That's new for me.
> linux kernel is not for casual readers.
Sure.
Regards
Stanislaw
Powered by blists - more mailing lists