From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 0/4] fs: nfs: Fix buffer overflows
Date: Thu, 06 Nov 2025 14:23:20 +0100 [thread overview]
Message-ID: <176243540058.723366.15553391837340584497.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20251104-nfs-v1-0-3e69e5c82a41@pengutronix.de>
On Tue, 04 Nov 2025 09:08:04 +0100, Sascha Hauer wrote:
> The NFS does hardly any checks on incoming packets. It blindly trusts
> the length values in packets and happily reads past the packets. This
> series introduces a function to read from packets concentrating the
> boundary checks in a single place. Also some other things I stumbled
> upon along the way.
>
>
> [...]
Applied, thanks!
[1/4] fs: nfs: drop PROG_NFS special casing
https://git.pengutronix.de/cgit/barebox/commit/?id=dbdfa94f2408 (link may not be stable)
[2/4] fs: nfs: do not read past packets
https://git.pengutronix.de/cgit/barebox/commit/?id=5be38817bc77 (link may not be stable)
[3/4] fs: nfs: use dev_* for messages
https://git.pengutronix.de/cgit/barebox/commit/?id=c847a2e42ce3 (link may not be stable)
[4/4] fs: nfs: reduce unwanted message to debug level
https://git.pengutronix.de/cgit/barebox/commit/?id=5789cb9767ba (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-11-06 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 8:08 Sascha Hauer
2025-11-04 8:08 ` [PATCH 1/4] fs: nfs: drop PROG_NFS special casing Sascha Hauer
2025-11-04 8:08 ` [PATCH 2/4] fs: nfs: do not read past packets Sascha Hauer
2025-11-04 8:08 ` [PATCH 3/4] fs: nfs: use dev_* for messages Sascha Hauer
2025-11-04 8:08 ` [PATCH 4/4] fs: nfs: reduce unwanted message to debug level Sascha Hauer
2025-11-06 13:23 ` Sascha Hauer [this message]
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=176243540058.723366.15553391837340584497.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox