From: Nguyen Duy Nhat Anh <neganhat@gmail.com>
To: adrianox@gmail.com
Cc: code@tyhicks.com, ecryptfs@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
syzbot+03c68e42ce4b33f7ce9b@syzkaller.appspotmail.com
Subject: Re: ecryptfs: validate auth tok payload size
Date: Sun, 4 Oct 2026 00:13:52 +0700 [thread overview]
Message-ID: <20261003171352.10244-1-neganhat@gmail.com> (raw)
In-Reply-To: <20261001213915.1326602-1-adrianox@gmail.com>
Hi Adriano,
I noticed this patch touches the exact same lines as a bug fix I submitted
earlier for ecryptfs (the ecryptfs_get_key_payload_data fix):
https://lore.kernel.org/all/20260917044558.41677-1-neganhat@gmail.com/T/
Since your patch expands on this area, could you please add my
Co-developed-by or Reported-by tag to this series?
Thanks,
Anh
next prev parent reply other threads:[~2026-10-03 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 21:39 [PATCH] " Adriano Cordova
2026-10-03 17:13 ` Nguyen Duy Nhat Anh [this message]
2026-10-04 12:31 ` Adriano Córdova
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=20261003171352.10244-1-neganhat@gmail.com \
--to=neganhat@gmail.com \
--cc=adrianox@gmail.com \
--cc=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+03c68e42ce4b33f7ce9b@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®