linux-kernel - Re: linux-next: build failure after merge of the amdgpu tree

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]

Date:   Mon, 11 Oct 2021 07:57:17 +0000
From:   Simon Ser <contact@...rsion.fr>
To:     Christoph Hellwig <hch@....de>
Cc:     Alex Deucher <alexdeucher@...il.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Daniel Vetter <daniel@...ll.ch>
Subject: Re: linux-next: build failure after merge of the amdgpu tree

On Monday, October 11th, 2021 at 09:51, Christoph Hellwig <hch@....de> wrote:

> On Mon, Oct 11, 2021 at 07:49:44AM +0000, Simon Ser wrote:
> > Have you heard about the kernel no-regression rule? Here, we can't enable a new
> > feature because that would regress user-space which mis-uses the kernel uAPI.
>
> Then you can't enable the feature without an explicit opt-in from
> userspace.  This ain't rocket science.

No, we can't have a "I_AM_NOT_BROKEN" ioctl for each and every uAPI mis-use.
User-space detection has been determined to be the best course of action.

> > If your reply wasn't aggressive, I don't know what it is.
>
> If there is one thing I find agressive it is your extreme passive
> aggressive behavior.

Come on. I'm just asking you to be civil, that's all. But that seems too much.

* * *

I guess I'll just inline these functions in the driver then, if a revert will
be NACK'ed by you?