From: "Theodore Tso" <tytso@mit.edu>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Mark Brown <broonie@kernel.org>,
Leandro Ribeiro <leandro.ribeiro@collabora.com>,
Pekka Paalanen <pekka.paalanen@collabora.com>,
Daniel Stone <daniels@collabora.com>,
Alexander Potapenko <glider@google.com>,
Christoph Hellwig <hch@infradead.org>,
Aleksandr Nogikh <nogikh@google.com>,
Boqun Feng <boqun@kernel.org>, Gary Guo <gary@garyguo.net>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
peterz@infradead.org, will@kernel.org, longman@redhat.com,
mingo@kernel.org, gregkh@linuxfoundation.org
Subject: Re: Policy regarding linux-next only changes
Date: Tue, 28 Jul 2026 21:46:21 -0400 [thread overview]
Message-ID: <amlXC0hahHo4Cdsx@mit.edu> (raw)
In-Reply-To: <bff95de5-7f0b-4f08-8ceb-58a6e354ebe2@I-love.SAKURA.ne.jp>
On Wed, Jul 29, 2026 at 08:46:16AM -0500, Tetsuo Handa wrote:
> >
> > i.e. I was wondering whether the system could ignore the "WARNING:"s
> > (and avoid the kernel panicking on them etc.) until after boot, i.e.
> > when the fuzzing starts.
It could, but it would involve making a change in syzbot.
Specifically, syzbot would have to be changed to boot the kernel being
tested without the kernel.panic_on_warn=1 boot command line function,
and then in the syzbot reproducer, to add the moral equivalent of
echo 1 > /proc/sys/kernel/panic_on_warn
> Commit 860e748bddcc ("drm: ensure blend mode supported if pixel format
> with alpha exposed") must be reverted or updated not to emit "WARNING:" string.
> Until authors of that commit respond, that commit had better be excluded from
> the linux-next tree.
There appears to be a fix which has been reviewed; I found it by
searching lore.kernel.org for the string "drm: ensure blend mode":
https://lore.kernel.org/all/CAPM=9txcOcnnxznq41z8+FA_V2BCqmRKFZBOt0oEhcHbBs8Fsg@mail.gmail.com/
- Ted
next prev parent reply other threads:[~2026-07-29 1:48 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 11:49 Policy regarding linux-next only changes Gary Guo
2026-07-02 12:49 ` Tetsuo Handa
2026-07-02 13:37 ` Miguel Ojeda
2026-07-02 14:11 ` Boqun Feng
2026-07-04 10:14 ` Tetsuo Handa
2026-07-04 12:06 ` Miguel Ojeda
2026-07-04 13:22 ` Theodore Tso
2026-07-05 11:36 ` Tetsuo Handa
2026-07-05 12:02 ` Miguel Ojeda
2026-07-05 12:06 ` Miguel Ojeda
2026-07-05 12:20 ` Mark Brown
2026-07-05 12:06 ` Mark Brown
2026-07-05 14:16 ` Tetsuo Handa
2026-07-06 17:23 ` Mark Brown
2026-07-20 10:06 ` Tetsuo Handa
2026-07-21 9:38 ` Alexander Potapenko
2026-07-21 11:48 ` Tetsuo Handa
2026-07-22 14:19 ` Alexander Potapenko
2026-07-22 15:07 ` Tetsuo Handa
2026-07-22 17:47 ` Theodore Tso
2026-07-24 12:11 ` Tetsuo Handa
2026-07-24 13:50 ` Theodore Tso
2026-07-24 14:35 ` Tetsuo Handa
2026-07-24 14:51 ` Theodore Tso
2026-07-24 15:29 ` Tetsuo Handa
2026-07-24 21:05 ` Theodore Tso
2026-07-25 5:20 ` Tetsuo Handa
2026-07-25 22:00 ` Theodore Tso
2026-07-24 17:49 ` Miguel Ojeda
2026-07-25 3:44 ` Tetsuo Handa
2026-07-25 9:38 ` Miguel Ojeda
2026-07-25 10:38 ` Tetsuo Handa
2026-07-25 13:27 ` Boqun Feng
2026-07-26 17:49 ` Mark Brown
2026-07-27 3:56 ` Theodore Tso
2026-07-27 13:19 ` Tetsuo Handa
2026-07-27 17:39 ` Mark Brown
2026-07-28 14:46 ` Tetsuo Handa
2026-07-28 15:16 ` Mark Brown
2026-07-28 22:11 ` Miguel Ojeda
2026-07-28 23:46 ` Tetsuo Handa
2026-07-29 1:46 ` Theodore Tso [this message]
2026-07-29 7:17 ` Miguel Ojeda
2026-07-29 7:12 ` Miguel Ojeda
2026-07-05 9:05 ` [PATCH] lockdep: Enable the printing of held locks of running non-current tasks (was: Policy regarding linux-next only changes) Ingo Molnar
2026-07-05 11:05 ` [PATCH] lockdep: Enable the printing of held locks of running non-current tasks Tetsuo Handa
2026-07-07 7:20 ` [PATCH -v2] lockdep: Enable the printing of held locks of remote running tasks and print task CPU Ingo Molnar
2026-07-07 13:10 ` Tetsuo Handa
2026-07-08 8:37 ` Ingo Molnar
2026-07-07 7:21 ` [tip: locking/debug] " tip-bot2 for Ingo Molnar
2026-07-08 8:41 ` [tip: locking/core] " tip-bot2 for Ingo Molnar
2026-07-05 14:59 ` Policy regarding linux-next only changes Boqun Feng
2026-07-02 13:22 ` Mark Brown
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=amlXC0hahHo4Cdsx@mit.edu \
--to=tytso@mit.edu \
--cc=boqun@kernel.org \
--cc=broonie@kernel.org \
--cc=daniels@collabora.com \
--cc=gary@garyguo.net \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=leandro.ribeiro@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=longman@redhat.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=nogikh@google.com \
--cc=ojeda@kernel.org \
--cc=pekka.paalanen@collabora.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.