linux-kernel - Re: [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <a8d56238-ae16-4b15-f60d-731f267737f4@landley.net>
Date:   Tue, 19 Sep 2017 22:29:54 -0500
From:   Rob Landley <rob@...dley.net>
To:     Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:     Christophe LEROY <christophe.leroy@....fr>,
        Michael Ellerman <mpe@...erman.id.au>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        sachinp <sachinp@...ux.vnet.ibm.com>, mhocko@...e.com,
        peterz@...radead.org, viresh.kumar@...aro.org,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        mingo@...nel.org, lokeshvutla@...com,
        Abdul Haleem <abdhalee@...ux.vnet.ibm.com>,
        linux-input@...r.kernel.org, thomas.lendacky@....com,
        lauraa@...eaurora.org, keescook@...omium.org,
        Jiri Kosina <jikos@...nel.org>, rostedt@...dmis.org,
        linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
        tglx@...utronix.de, gregkh@...uxfoundation.org,
        linux-kernel@...r.kernel.org, tj@...nel.org,
        Andrew Morton <akpm@...ux-foundation.org>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH v3] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

On 09/17/2017 08:51 AM, Henrique de Moraes Holschuh wrote:
> On Sat, 16 Sep 2017, Rob Landley wrote:
>> So, I added a workaround with a printk in hopes of embarassing them into
>> someday fixing it.
> 
> Oh, it will be fixed in Debian alright.

Cool!

But part of the problem is people upgrade the kernel on existing
deployed root filesystems, some of which are a fork off of a fork off of
debian, so we won't exhaust the broken userspace for probably a couple
years.

I'd put it in feature-removal-schedule.txt but Linus zapped that, so...

> I am just waiting the issue to
> settle a bit to file the bug reports, or maybe even send in the Debian
> patches myself (note that I am not responsible for the code in question,
> so I am not wearing a brown paperbag at this time).  Even if I didn't do
> it, there are several other Debian Developers reading LKML that could do
> it (provided they noticed this specific thread and are aware of the
> situation) :p

There was a previous thread last merge window they didn't notice. I was
hoping the warning would be obvious enough. :)

> I can even push for the fixes to be accepted into the stable and
> oldstable branches of Debian, but that can take anything from a few
> weeks to several months, due to the way our stable releases work.  But
> it would eventually happen.
> 
> Whether such fixes will ever make it to LTS branches, especially
> Ubuntu's, *that* I don't know.

I have no idea what that powerpc system was, the guy didn't say...

Rob