Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Andrew Paniakin <apanyaki@amazon.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Christian Heusel <christian@heusel.eu>, <pc@cjr.nz>,
	<stfrench@microsoft.com>, <sashal@kernel.org>, <pc@manguebit.com>,
	<stable@vger.kernel.org>, <linux-cifs@vger.kernel.org>,
	<abuehaze@amazon.com>, <simbarb@amazon.com>, <benh@amazon.com>,
	<gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION][BISECTED][STABLE] Commit 60e3318e3e900 in stable/linux-6.1.y breaks cifs client failover to another server in DFS namespace
Date: Fri, 9 May 2025 20:05:13 -0700	[thread overview]
Message-ID: <aB7CaTP-jwYhDROJ@3c06303d853a.ant.amazon.com> (raw)
In-Reply-To: <Z9cZuBxOscqybcMy@3c06303d853a.ant.amazon.com>

On 16/03/2025, Andrew Paniakin wrote:
> My next step is to resend 7ad54b98fc1f1 ("cifs: use origin fullpath for
> automounts") with required comments and send an update to this thread once it
> merged.

Backport with a fix was released in v6.1.135.

#regzbot fix: 7d8bb979f627 ("cifs: use origin fullpath for automounts")

      reply	other threads:[~2025-05-10  3:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 18:32 [REGRESSION][BISECTED] Commit 60e3318e3e900 in stable/linux-6.1.y breaks cifs client failover to another server in DFS namespace Andrew Paniakin
2024-06-24 17:59 ` Andrew Paniakin
2024-06-25 11:07   ` [REGRESSION][BISECTED][STABLE] " Christian Heusel
2024-06-26 22:09     ` Andrew Paniakin
2024-06-27 20:16       ` Christian Heusel
2024-07-11  9:49         ` Linux regression tracking (Thorsten Leemhuis)
2024-07-13  3:22           ` Andrew Paniakin
2024-07-23  0:51             ` Andrew Paniakin
2024-09-27 10:56               ` Linux regression tracking (Thorsten Leemhuis)
2024-10-16 20:49                 ` Andrew Paniakin
2024-11-10 17:59                   ` Andrew Paniakin
2025-03-16 18:34                     ` Andrew Paniakin
2025-05-10  3:05                       ` Andrew Paniakin [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=aB7CaTP-jwYhDROJ@3c06303d853a.ant.amazon.com \
    --to=apanyaki@amazon.com \
    --cc=abuehaze@amazon.com \
    --cc=benh@amazon.com \
    --cc=christian@heusel.eu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@cjr.nz \
    --cc=pc@manguebit.com \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=simbarb@amazon.com \
    --cc=stable@vger.kernel.org \
    --cc=stfrench@microsoft.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