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: Mon, 22 Jul 2024 17:51:14 -0700	[thread overview]
Message-ID: <Zp7-gl5mMFCb4UWa@3c06303d853a.ant.amazon.com> (raw)
In-Reply-To: <ZpHy4V6P-pawTG2f@3c06303d853a.ant.amazon.com>

On 12/07/2024, Andrew Paniakin wrote:
> On 11/07/2024, Linux regression tracking (Thorsten Leemhuis) wrote:
> > On 27.06.24 22:16, Christian Heusel wrote:
> > > On 24/06/26 03:09PM, Andrew Paniakin wrote:
> > >> On 25/06/2024, Christian Heusel wrote:
> > >>> On 24/06/24 10:59AM, Andrew Paniakin wrote:
> > >>>> On 19/06/2024, Andrew Paniakin wrote:
> > >>>>> Commit 60e3318e3e900 ("cifs: use fs_context for automounts") was
> 
> [snip]
> 
> > Hmmm, unless I'm missing something it seems nobody did so. Andrew, could
> > you take care of that to get this properly fixed to prevent others from
> > running into the same problem?
> > 
> > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> > --
> > Everything you wanna know about Linux kernel regression tracking:
> > https://linux-regtracking.leemhuis.info/about/#tldr
> > If I did something stupid, please tell me, as explained on that page.
> > 
> > #regzbot poke
> 
> We got the confirmation from requesters that the kernel with this patch
> works properly, our regression tests also passed, so I submitted
> backport request:
> https://lore.kernel.org/stable/20240713031147.20332-1-apanyaki@amazon.com/

There was an issue with backporting the follow-up fix for this patch:
https://lore.kernel.org/all/20240716152749.667492414@linuxfoundation.org/
I'll work on fixing this issue and send new patches again for the next cycle.

  reply	other threads:[~2024-07-23  0:51 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 [this message]
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

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=Zp7-gl5mMFCb4UWa@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