From: Tyler Hicks <code@tyhicks.com>
To: Yichong Chen <chenyichong@uniontech.com>
Cc: Thorsten Blum <thorsten.blum@linux.dev>,
Christian Brauner <brauner@kernel.org>,
Eric Biggers <ebiggers@kernel.org>, Kees Cook <kees@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] ecryptfs: split packet parser length fixes
Date: Tue, 21 Jul 2026 02:29:38 -0500 [thread overview]
Message-ID: <178461835000.30963.1159903948163576972.b4-ty@b4> (raw)
In-Reply-To: <cover.1784081896.git.chenyichong@uniontech.com>
On Wed, 15 Jul 2026 13:20:03 +0800, Yichong Chen wrote:
> This v2 splits the packet parser hardening into three separate fixes as
> requested by Tyler Hicks:
>
> 1. pass the actual packet set buffer size into ecryptfs_parse_packet_set()
> 2. fix the tag 11 exact-fit size check
> 3. reject too-small tag 70 packet bodies before size subtraction
>
> [...]
Thank you! They've been applied to the next branch of the tyhicks/ecryptfs.git tree.
You can find a direct link below but please be aware that the commit hash is
unstable and, therefore, the URL may not be valid in the future.
[1/3] ecryptfs: pass packet set buffer size to parser
https://git.kernel.org/tyhicks/ecryptfs/c/2602b79c5b3e2f6fce12e38a670f8e3fda4e46a2
[2/3] ecryptfs: fix tag 11 packet exact-fit size check
https://git.kernel.org/tyhicks/ecryptfs/c/8b2ec0f56f55477f547d332526c9ae2a8fabc0a5
[3/3] ecryptfs: reject too-small tag 70 packets
https://git.kernel.org/tyhicks/ecryptfs/c/e97bbe1b2bd82ec2ae37ad2e4965b4d3e78bbf7f
Tyler
prev parent reply other threads:[~2026-07-21 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 5:20 Yichong Chen
2026-07-15 5:20 ` [PATCH v2 1/3] ecryptfs: pass packet set buffer size to parser Yichong Chen
2026-07-15 5:20 ` [PATCH v2 2/3] ecryptfs: fix tag 11 packet exact-fit size check Yichong Chen
2026-07-15 5:20 ` [PATCH v2 3/3] ecryptfs: reject too-small tag 70 packets Yichong Chen
2026-07-21 7:29 ` Tyler Hicks [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=178461835000.30963.1159903948163576972.b4-ty@b4 \
--to=code@tyhicks.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chenyichong@uniontech.com \
--cc=ebiggers@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
/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
all inboxes | Powered by JetHome®