linux-kernel - Re: [PATCH v2 4/4] drm/panic: Add a qr

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: <2024070947-exorcism-purchase-2f28@gregkh>
Date: Tue, 9 Jul 2024 11:12:23 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Jocelyn Falempe <jfalempe@...hat.com>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	Maxime Ripard <mripard@...nel.org>,
	Thomas Zimmermann <tzimmermann@...e.de>,
	David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
	Miguel Ojeda <ojeda@...nel.org>,
	Alex Gaynor <alex.gaynor@...il.com>,
	Wedson Almeida Filho <wedsonaf@...il.com>,
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
	Bjorn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <benno.lossin@...ton.me>,
	Andreas Hindborg <a.hindborg@...sung.com>,
	Alice Ryhl <aliceryhl@...gle.com>, linux-kernel@...r.kernel.org,
	dri-devel@...ts.freedesktop.org, rust-for-linux@...r.kernel.org,
	Danilo Krummrich <dakr@...hat.com>
Subject: Re: [PATCH v2 4/4] drm/panic: Add a qr_code panic screen

On Tue, Jul 09, 2024 at 11:11:35AM +0200, Greg KH wrote:
> On Tue, Jul 09, 2024 at 10:40:10AM +0200, Jocelyn Falempe wrote:
> > +config DRM_PANIC_SCREEN_QR_CODE_URL
> > +	string "Base url of the QR code in the panic screen"
> > +	depends on DRM_PANIC_SCREEN_QR_CODE
> > +	help
> > +	  This option sets the base url to report the kernel panic. If it's set
> > +	  the qr code will contain the url and the kmsg compressed with zlib as
> > +	  url parameter. If it's empty, the qr code will contain the kmsg as
> > +	  uncompressed text only.
> 
> meta-comment, should we by default do this on a kernel.org domain so
> that no specific distro has to worry about hosing this type of web
> service?

Also, do you have the backend source for this to show how anyone can
host it themselves as well?  We can't add features to the kernel that no
one but closed-source implementations will use for obvious reasons.

thanks,

greg k-h