Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: "Reiterer, Horst" <horst.reiterer@fabasoft.com>,
	Steve French <smfrench@gmail.com>
Cc: "linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: RE: [PATCH] smb: client: fix chmod(2) regression with ATTR_READONLY
Date: Wed, 19 Feb 2025 10:49:39 -0300	[thread overview]
Message-ID: <47b814ccbd2eda970c13f1b68d1ff53b@manguebit.com> (raw)
In-Reply-To: <08e226c8df7246fbaf710f36b39ead4a@fabasoft.com>

"Reiterer, Horst" <horst.reiterer@fabasoft.com> writes:

> thanks, Steve and Paulo! Considering the severity (chmod does not take effect anymore) and the fact that this regression was caused by dropping a condition in two lines of code that is merely being restored by the fix (basically, it's a partial revert), is there any way to prioritize this change as there's no production-ready workaround? It's difficult to avoid updating to 6.6+ at this point.
>

It has been marked for -stable, so it's expected that stable team will
pick it up for v6.6+ once the fix is released in v6.14-rc4.  If for some
reason they miss it, I'll ping them to make sure it goes into the stable
trees.

  reply	other threads:[~2025-02-19 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 10:04 [PATCH] smb: client: fix chmod(2) regression with ATTR_READONLY Reiterer, Horst
2025-02-19 13:49 ` Paulo Alcantara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-16 21:02 Paulo Alcantara
2025-02-16 23:20 ` Steve French

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=47b814ccbd2eda970c13f1b68d1ff53b@manguebit.com \
    --to=pc@manguebit.com \
    --cc=horst.reiterer@fabasoft.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.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