linux-kernel - Re: [PATCH] docs: driver-api: firmware: clarify userspace requirements

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: <CAPM=9tzv+=+ZGRtHgapUVAiDjHn=Bp33BqyLLQKDuKsR-AoC7A@mail.gmail.com>
Date: Tue, 18 Mar 2025 08:56:41 +1000
From: Dave Airlie <airlied@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>, linux-doc@...r.kernel.org, 
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org, 
	simona.vetter@...ll.ch
Subject: Re: [PATCH] docs: driver-api: firmware: clarify userspace requirements

On Tue, 18 Mar 2025 at 08:53, Jonathan Corbet <corbet@....net> wrote:
>
> Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com> writes:
>
> > The guidelines mention that firmware updates can't break the kernel,
> > but it doesn't state directly that they can't break userspace programs.
> > Make it explicit that firmware updates cannot break UAPI.
> >
> > Signed-off-by: Jacek Lawrynowicz <jacek.lawrynowicz@...ux.intel.com>
> > ---
> >  .../driver-api/firmware/firmware-usage-guidelines.rst        | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/Documentation/driver-api/firmware/firmware-usage-guidelines.rst b/Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> > index fdcfce42c6d28..5f8f13e2ee510 100644
> > --- a/Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> > +++ b/Documentation/driver-api/firmware/firmware-usage-guidelines.rst
> > @@ -42,3 +42,8 @@ then of course these rules will not apply strictly.)
> >    deprecating old major versions, then this should only be done as a
> >    last option, and be stated clearly in all communications.
> >
> > +* Firmware files that affect the User API (UAPI) shall not introduce
> > +  changes that break existing userspace programs. Updates to such firmware
> > +  must ensure backward compatibility with existing userspace applications.
> > +  This includes maintaining consistent interfaces and behaviors that
> > +  userspace programs rely on.
> > \ No newline at end of file
>
> This ^^^^^^^^^^^^^^^^^^^^^^^^  is a good thing to avoid.  That can be
> fixed up at apply time.
>
> Dave, you're the only one with fingerprints on this document; is the
> change OK with you?

LGTM,

Acked-by: Dave Airlie <airlied@...hat.com>

Dave.

>
> Thanks,
>
> jon