rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jocelyn Falempe <jfalempe@redhat.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Miguel Ojeda <ojeda@kernel.org>,
	Alex Gaynor <alex.gaynor@gmail.com>,
	Wedson Almeida Filho <wedsonaf@gmail.com>,
	Boqun Feng <boqun.feng@gmail.com>, Gary Guo <gary@garyguo.net>,
	Bjorn Roy Baron <bjorn3_gh@protonmail.com>,
	Benno Lossin <benno.lossin@proton.me>,
	Andreas Hindborg <a.hindborg@samsung.com>,
	Alice Ryhl <aliceryhl@google.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	rust-for-linux@vger.kernel.org,
	Danilo Krummrich <dakr@redhat.com>
Subject: Re: [PATCH v2 4/4] drm/panic: Add a qr_code panic screen
Date: Tue, 9 Jul 2024 12:12:24 +0200	[thread overview]
Message-ID: <2024070944-follow-crazy-ff95@gregkh> (raw)
In-Reply-To: <acd5c505-f058-46e7-9d92-620dea41d707@redhat.com>

On Tue, Jul 09, 2024 at 12:04:02PM +0200, Jocelyn Falempe wrote:
> 
> 
> On 09/07/2024 11:12, Greg KH wrote:
> > 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.
> 
> I've made a proof of concept backend here:
> https://github.com/kdj0c/panic_report/
> 
> And the javascript to decode the kmsg trace is here (under MIT licence):
> https://github.com/kdj0c/panic_report/blob/main/docs/panic_report.js

SPDX lines are your friend, you might want to look into that for this
stuff :)

> It uses the pako js library to uncompress the zlib data, which is also under
> MIT/Zlib licence https://github.com/nodeca/pako/

Great, can you put that in the Kconfig help area for this option in your
next version?

> If kernel.org want to host a default service for that, that would be great.
> It can be linked with https://bugzilla.kernel.org to easily create a bug, or
> look for similar bugs.

Someone should at least propose it if this is going to be an option that
the kernel supports.

thanks,

greg k-h

  reply	other threads:[~2024-07-09 10:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  8:40 [PATCH v2 0/4] drm/panic: Add a qr_code panic screen Jocelyn Falempe
2024-07-09  8:40 ` [PATCH v2 1/4] drm/panic: Add integer scaling to blit() Jocelyn Falempe
2024-07-09  8:40 ` [PATCH v2 2/4] drm/rect: add drm_rect_overlap() Jocelyn Falempe
2024-07-09  8:40 ` [PATCH v2 3/4] drm/panic: simplify logo handling Jocelyn Falempe
2024-07-09  8:40 ` [PATCH v2 4/4] drm/panic: Add a qr_code panic screen Jocelyn Falempe
2024-07-09  9:11   ` Greg KH
2024-07-09  9:12     ` Greg KH
2024-07-09 10:04       ` Jocelyn Falempe
2024-07-09 10:12         ` Greg KH [this message]
2024-07-09 12:02           ` Jocelyn Falempe
2024-07-09  9:41   ` Miguel Ojeda
2024-07-09 15:09     ` Jocelyn Falempe
2024-07-10  9:00       ` Miguel Ojeda
2024-07-09  9:41   ` Alice Ryhl
2024-07-09 15:21     ` Jocelyn Falempe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2024070944-follow-crazy-ff95@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=a.hindborg@samsung.com \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=jfalempe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=wedsonaf@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).