From: Al Viro <viro@zeniv.linux.org.uk>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Kees Cook <kees@kernel.org>,
Ronald Monthero <debug.penguin32@gmail.com>,
al@alarsen.net, gustavoars@kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] qnx4: fix to avoid panic due to buffer overflow
Date: Sun, 23 Feb 2025 00:19:13 +0000 [thread overview]
Message-ID: <20250223001913.GQ1977892@ZenIV> (raw)
In-Reply-To: <CAGudoHHB6CsVntmBTgXd_nP727eGg6xr_cPe2=p6FyAN=rTvzw@mail.gmail.com>
On Sat, Feb 22, 2025 at 01:12:47PM +0100, Mateusz Guzik wrote:
> General tune is not holding the codebase hostage to obsolete (and
> probably not at all operational) components. If in doubt, prune it.
What exactly is being held hostage, though? Do we have an API change
that gets blocked just by the old filesystems and if so, which one
it is?
next prev parent reply other threads:[~2025-02-23 0:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 9:53 [PATCH] qnx4: fix to avoid panic due to buffer overflow Ronald Monthero
2023-11-12 16:16 ` Anders Larsen
2023-11-13 9:25 ` Ronald Monthero
2023-11-13 15:40 ` Anders Larsen
2023-11-14 14:38 ` Ronald Monthero
2023-11-16 14:29 ` Kees Cook
2023-11-16 14:58 ` Kees Cook
2023-11-16 16:48 ` Anders Larsen
2023-11-16 18:26 ` Kees Cook
2023-11-18 8:38 ` Ronald Monthero
2025-02-21 14:51 ` Mateusz Guzik
2025-02-21 17:38 ` Kees Cook
2025-02-22 12:12 ` Mateusz Guzik
2025-02-22 15:17 ` Kees Cook
2025-02-22 16:36 ` Mateusz Guzik
2025-02-24 11:26 ` Christian Brauner
2025-02-23 0:19 ` Al Viro [this message]
2025-02-24 11:56 ` Mateusz Guzik
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=20250223001913.GQ1977892@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=al@alarsen.net \
--cc=brauner@kernel.org \
--cc=debug.penguin32@gmail.com \
--cc=gustavoars@kernel.org \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@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