linux-kernel - Re: [BUG] Build failure and alleged fix for next-20240523

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: <4f821c7f-6201-470f-b39d-ba689ca027d9@paulmck-laptop>
Date: Thu, 30 May 2024 09:55:55 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Abhinav Kumar <quic_abhinavk@...cinc.com>
Cc: sfr@...b.auug.org.au, Rob Clark <robdclark@...il.com>,
	Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
	Sean Paul <sean@...rly.run>,
	Marijn Suijten <marijn.suijten@...ainline.org>,
	David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
	Jon Hunter <jonathanh@...dia.com>, linux-arm-msm@...r.kernel.org,
	dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] Build failure and alleged fix for next-20240523

On Fri, May 24, 2024 at 12:57:58PM -0700, Abhinav Kumar wrote:
> Hello
> 
> On 5/24/2024 12:55 PM, Paul E. McKenney wrote:
> > Hello!
> > 
> > I get the following allmodconfig build error on x86 in next-20240523:
> > 
> > Traceback (most recent call last):
> >    File "drivers/gpu/drm/msm/registers/gen_header.py", line 970, in <module>
> >      main()
> >    File "drivers/gpu/drm/msm/registers/gen_header.py", line 951, in main
> >      parser.add_argument('--validate', action=argparse.BooleanOptionalAction)
> > AttributeError: module 'argparse' has no attribute 'BooleanOptionalAction'
> > 
> > The following patch allows the build to complete successfully:
> > 
> > https://patchwork.kernel.org/project/dri-devel/patch/20240508091751.336654-1-jonathanh@nvidia.com/#25842751
> > 
> > As to whether this is a proper fix, I must defer to the DRM folks on CC.
> 
> Thanks for the report.
> 
> I have raised a merge request for
> https://patchwork.freedesktop.org/patch/593057/ to make it available for the
> next fixes release for msm.

Thank you!

This still is not in -next, so I am putting it into -rcu just to silence
the diagnostic.  Or should I push this to mainline via -rcu?

							Thanx, Paul