From: Sheng Yong <shengyong2021@gmail.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: shengyong2021@gmail.com, shengyong1@xiaomi.com,
LKML <linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] erofs: limit the level of fs stacking for file-backed mounts
Date: Sat, 22 Nov 2025 10:56:18 +0800 [thread overview]
Message-ID: <bb3101cb-21cf-4f36-9130-4482a531c344@gmail.com> (raw)
In-Reply-To: <20251121134647.104354-1-hsiangkao@linux.alibaba.com>
On 11/21/25 21:46, Gao Xiang wrote:
> Otherwise, it could cause potential kernel stack overflow (e.g., EROFS
> mounting itself).
>
> Fixes: fb176750266a ("erofs: add file-backed mount support")
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Reviewed-by: Sheng Yong <shengyong1@xiaomi.com>
thanks,
shengyong
next prev parent reply other threads:[~2025-11-22 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 13:46 [PATCH] erofs: limit the level of fs stacking for file-backed mounts Gao Xiang
2025-11-22 2:56 ` Sheng Yong [this message]
2025-11-22 6:23 ` [PATCH v2] " Gao Xiang
2025-11-24 0:46 ` Chao Yu
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=bb3101cb-21cf-4f36-9130-4482a531c344@gmail.com \
--to=shengyong2021@gmail.com \
--cc=brauner@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shengyong1@xiaomi.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