public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Ilya Dryomov <idryomov@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6] ceph: give up on paths longer than PATH_MAX
Date: Wed,  8 Jan 2025 14:49:47 -0500	[thread overview]
Message-ID: <20250107141116-9da07b060df44667@stable.kernel.org> (raw)
In-Reply-To: <20250107155010.2658845-1-idryomov@gmail.com>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 550f7ca98ee028a606aa75705a7e77b1bd11720f

WARNING: Author mismatch between patch and upstream commit:
Backport author: Ilya Dryomov<idryomov@gmail.com>
Commit author: Max Kellermann<max.kellermann@ionos.com>


Status in newer kernel trees:
6.12.y | Present (different SHA1: 99a37ab76a31)
6.6.y | Present (different SHA1: 82dfe5074a06)

Note: The patch differs from the upstream commit:
---
1:  550f7ca98ee0 ! 1:  092e42aac21a ceph: give up on paths longer than PATH_MAX
    @@ Metadata
      ## Commit message ##
         ceph: give up on paths longer than PATH_MAX
     
    +    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
    @@ Commit message
         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 ##
     @@ fs/ceph/mds_client.c: char *ceph_mdsc_build_path(struct ceph_mds_client *mdsc, struct dentry *dentry,
    @@ fs/ceph/mds_client.c: char *ceph_mdsc_build_path(struct ceph_mds_client *mdsc, s
     +		 * cannot ever succeed.  Creating paths that long is
     +		 * possible with Ceph, but Linux cannot use them.
      		 */
    --		pr_warn_client(cl, "did not end path lookup where expected (pos = %d)\n",
    --			       pos);
    +-		pr_warn("build_path did not end path lookup where expected (pos = %d)\n",
    +-			pos);
     -		goto retry;
     +		return ERR_PTR(-ENAMETOOLONG);
      	}
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Success   |

  reply	other threads:[~2025-01-08 19:49 UTC|newest]

Thread overview: 3+ 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-08 19:49 ` Sasha Levin [this message]
2025-01-09 11:46 ` Greg Kroah-Hartman

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=20250107141116-9da07b060df44667@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=idryomov@gmail.com \
    --cc=stable@vger.kernel.org \
    /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