From: Eric Biggers <ebiggers@kernel.org>
To: Qing Wang <wangqing7171@gmail.com>
Cc: jaegeuk@kernel.org, linux-fscrypt@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+d130f98b2c265fae5297@syzkaller.appspotmail.com,
tytso@mit.edu
Subject: Re: [PATCH v2] fscrypt: Fix uninit-value in ovl_fill_real
Date: Mon, 26 Jan 2026 19:47:54 -0800 [thread overview]
Message-ID: <20260127034754.GA4470@sol> (raw)
In-Reply-To: <20260126062216.496560-1-wangqing7171@gmail.com>
On Mon, Jan 26, 2026 at 02:22:16PM +0800, Qing Wang wrote:
> ---
> fs/overlayfs/readdir.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This is an overlayfs patch, so please title it appropriately and use
get_maintainer.pl to get the correct recipients. You can leave
linux-fscrypt@vger.kernel.org on Cc.
- Eric
next prev parent reply other threads:[~2026-01-27 3:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 7:30 [PATCH] fscrypt: Fix uninit-value in ovl_fill_real Qing Wang
2026-01-24 18:25 ` Eric Biggers
2026-01-26 6:22 ` [PATCH v2] " Qing Wang
2026-01-27 3:47 ` Eric Biggers [this message]
2026-01-27 6:10 ` [PATCH] " Qing Wang
2026-01-26 6:33 ` Qing Wang
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=20260127034754.GA4470@sol \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+d130f98b2c265fae5297@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
--cc=wangqing7171@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