linux-kernel - Re: more PID churn during boot?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 10 Jan 2012 11:25:00 -0800
From:	Tony Luck <tony.luck@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: more PID churn during boot?

On Mon, Jan 9, 2012 at 5:14 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> while the 2012 editions print:
>>
>> udevd (341): /proc/341/oom_adj is deprecated, please use
>> /proc/341/oom_score_adj instead.

Ok - not a kernel problem. Building old kernels (that used to not have this
much churn) while checking for the start point for a bisect started showing
the same churn.

I tracked the start of the problem to when I updated my build machine
on jan 3rd - and it's now throwing a new version of udevd[*] into the initrd
that I throw at my test machine.
Probably a bunch of other initrd components are new versions too.

-Tony

[1] Builds since Jan 3rd all have this extra line in dmesg log:
udev: starting version 147
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/