mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffrey E Altman <jaltman@auristor.com>
To: linux-stable <stable@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Backport request: commit 29be9100aca2915fab54b5693309bc42956542e5 ("afs: Don't cross .backup mountpoint from backup volume")
Date: Tue, 4 Jun 2024 11:50:06 -0400	[thread overview]
Message-ID: <2f3691b1-4f19-4a21-b235-a46ae54b8424@auristor.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

Please backport to the following patch which was merged upstream.

It should apply to linux-5.4.y and later.

commit 29be9100aca2915fab54b5693309bc42956542e5
Author: Marc Dionne <marc.dionne@auristor.com>1
Date:   Fri May 24 17:17:55 2024 +0100

     afs: Don't cross .backup mountpoint from backup volume

     Don't cross a mountpoint that explicitly specifies a backup volume
     (target is <vol>.backup) when starting from a backup volume.

     It it not uncommon to mount a volume's backup directly in the volume
     itself.  This can cause tools that are not paying attention to get
     into a loop mounting the volume onto itself as they attempt to
     traverse the tree, leading to a variety of problems.

     This doesn't prevent the general case of loops in a sequence of
     mountpoints, but addresses a common special case in the same way
     as other afs clients.

     Reported-by: Jan Henrik Sylvester <jan.henrik.sylvester@uni-hamburg.de>
     Link: 
http://lists.infradead.org/pipermail/linux-afs/2024-May/008454.html
     Reported-by: Markus Suvanto <markus.suvanto@gmail.com>
     Link: 
http://lists.infradead.org/pipermail/linux-afs/2024-February/008074.html
     Signed-off-by: Marc Dionne <marc.dionne@auristor.com>
     Signed-off-by: David Howells <dhowells@redhat.com>
     Link: 
https://lore.kernel.org/r/768760.1716567475@warthog.procyon.org.uk
     Reviewed-by: Jeffrey Altman <jaltman@auristor.com>
     cc: linux-afs@lists.infradead.org
     Signed-off-by: Christian Brauner <brauner@kernel.org>

Thank you.

Jeffrey Altman




[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4039 bytes --]

             reply	other threads:[~2024-06-04 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 15:50 Jeffrey E Altman [this message]
2024-06-12 12:31 ` Greg KH

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=2f3691b1-4f19-4a21-b235-a46ae54b8424@auristor.com \
    --to=jaltman@auristor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®