From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
Xiubo Li <xiubli@redhat.com>,
Patrick Donnelly <pdonnell@redhat.com>,
Milind Changire <mchangir@redhat.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6] ceph: give up on paths longer than PATH_MAX
Date: Thu, 9 Jan 2025 12:46:30 +0100 [thread overview]
Message-ID: <2025010912-deputize-frolic-7381@gregkh> (raw)
In-Reply-To: <20250107155010.2658845-1-idryomov@gmail.com>
On Tue, Jan 07, 2025 at 04:50:08PM +0100, Ilya Dryomov wrote:
> From: Max Kellermann <max.kellermann@ionos.com>
>
> commit 550f7ca98ee028a606aa75705a7e77b1bd11720f upstream.
>
> If the full path to be built by ceph_mdsc_build_path() happens to be
> longer than PATH_MAX, then this function will enter an endless (retry)
> loop, effectively blocking the whole task. Most of the machine
> becomes unusable, making this a very simple and effective DoS
> vulnerability.
>
> I cannot imagine why this retry was ever implemented, but it seems
> rather useless and harmful to me. Let's remove it and fail with
> ENAMETOOLONG instead.
>
> Cc: stable@vger.kernel.org
> Reported-by: Dario Weißer <dario@cure53.de>
> Signed-off-by: Max Kellermann <max.kellermann@ionos.com>
> Reviewed-by: Alex Markuze <amarkuze@redhat.com>
> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
> [idryomov@gmail.com: backport to 6.6: pr_warn() is still in use]
> ---
> fs/ceph/mds_client.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
Thank you, I've dropped the "large" ceph patches from 6.6.y now and
added this one instead.
greg k-h
prev parent reply other threads:[~2025-01-09 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 15:50 [PATCH 6.6] ceph: give up on paths longer than PATH_MAX Ilya Dryomov
2025-01-09 11:46 ` Greg Kroah-Hartman [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=2025010912-deputize-frolic-7381@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=idryomov@gmail.com \
--cc=mchangir@redhat.com \
--cc=patches@lists.linux.dev \
--cc=pdonnell@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xiubli@redhat.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