Re: Why almost every command is trying to read urandom?

2019-11-12 Thread Lauri Kasanen
On Tue, 12 Nov 2019 22:43:28 +0100 Mauro Condarelli wrote: > Question: is that supposed to be a "harmless warning" or it's the tip of > an iceberg? It's harmless as long as the program causing it is not cryptographic. "The randomness provided may not be high quality". - Lauri

Re: Why almost every command is trying to read urandom?

2019-11-12 Thread Mauro Condarelli
On 11/12/19 10:12 PM, Michael Conrad wrote: > I hadn't noticed before, but I just checked and my busybox 1.11 is > doing this (reading /dev/urandom on every single applet startup) but I > have a later busybox 1.30 which does not. I'm currently using busybox-1.31.0 >    strace busybox echo 2>&1

Re: Why almost every command is trying to read urandom?

2019-11-12 Thread Michael Conrad
On 11/12/19 2:47 PM, Mauro Condarelli wrote: In a recent kernel(5.x) / Buildroot / Busybox for an embedded system (mips/MT7628, if it matters) I see TONS of: |random: mount: uninitialized urandom read (4 bytes read) random: fsck.vfat: uninitialized urandom read (4 bytes read) random: tar:

Why almost every command is trying to read urandom?

2019-11-12 Thread Mauro Condarelli
In a recent kernel(5.x) / Buildroot / Busybox for an embedded system (mips/MT7628, if it matters) I see TONS of: |random: mount: uninitialized urandom read (4 bytes read) random: fsck.vfat: uninitialized urandom read (4 bytes read) random: tar: uninitialized urandom read (4 bytes read) (Complete

Re: [PATCH] Remove stime() function calls

2019-11-12 Thread Alistair Francis
On Sat, 2019-11-09 at 01:55 +0100, Bernhard Reutner-Fischer wrote: > On 8 November 2019 23:26:48 CET, Alistair Francis < > alistair.fran...@wdc.com> wrote: > > On Wed, 2019-11-06 at 09:17 +0100, walter harms wrote: > > > Your are right but so far i understand > > > the idea here is to have a

Re: immediate segmentation fault with LLVM/Clang 9

2019-11-12 Thread Khem Raj
On Tue, Nov 12, 2019 at 6:03 AM Romain Naour wrote: > > Hi Denys, > > Le 08/11/2019 à 14:54, Denys Vlasenko a écrit : > > On Fri, Nov 8, 2019 at 10:04 AM Romain Naour wrote: > >> Le 28/10/2019 à 08:23, David Demelier a écrit : > >>> Le 25/10/2019 à 10:00, Romain Naour a écrit : > There is

Re: immediate segmentation fault with LLVM/Clang 9

2019-11-12 Thread Romain Naour
Hi Denys, Le 08/11/2019 à 14:54, Denys Vlasenko a écrit : > On Fri, Nov 8, 2019 at 10:04 AM Romain Naour wrote: >> Le 28/10/2019 à 08:23, David Demelier a écrit : >>> Le 25/10/2019 à 10:00, Romain Naour a écrit : There is an initial patch for this issue:

[PATCH 1/2] iproute: codeshrink netlink message length check

2019-11-12 Thread Natanael Copa
reduce size by de-duplicate netlink message length check function old new delta check_nlmsg_len- 22 +22 print_route 19011893 -8 print_neigh

[PATCH 2/2] iproute: codeshrink initalization of netlink request

2019-11-12 Thread Natanael Copa
reduce size by de-duplicate initialization of netlink reqest structure initialization. function old new delta init_rtnlmsg_rtmsg_req - 34 +34 init_nlmsg_ifinfomsg_req - 34