All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Reiterer, Horst" <horst.reiterer@fabasoft.com>
To: "pc@manguebit.com" <pc@manguebit.com>
Cc: "linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>
Subject: RE: Regression: smb: chmod ignored (5.14.0-427.40.1.el9_4 vs. 5.14.0-503.15.1.el9_5)
Date: Sat, 25 Jan 2025 22:22:43 +0000	[thread overview]
Message-ID: <e70df2a91d1346fdbe88463d4edbf05c@fabasoft.com> (raw)

Hi Paulo,

thanks for testing with mainline. Bug created:

https://bugzilla.kernel.org/show_bug.cgi?id=219724

Cheers,

Horst Reiterer

-----Ursprüngliche Nachricht-----
Von: Paulo Alcantara <pc@manguebit.com> 
Gesendet: Samstag, 25. Januar 2025 15:25
An: Reiterer, Horst <horst.reiterer@fabasoft.com>; linux-cifs@vger.kernel.org
Betreff: Re: Regression: smb: chmod ignored (5.14.0-427.40.1.el9_4 vs. 5.14.0-503.15.1.el9_5)

Hi,

Thanks for the report.

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

> after updating from AlmaLinux 9.4 to 9.5 
> (https://repo.almalinux.org/vault/9.4/BaseOS/Source/Packages/kernel-5.
> 14.0-427.40.1.el9_4.src.rpm vs. 
> https://repo.almalinux.org/vault/9.5/BaseOS/Source/Packages/kernel-5.1
> 4.0-503.15.1.el9_5.src.rpm), chmod gets ignored by the CIFS filesystem 
> when executed against a Windows file server unless chmod happens in 
> another process.

Yeah, I was able to reproduce it with mainline kernel as well.

Could you please file a bug [1] against File System -> CIFS component?

Thanks.

[1] https://bugzilla.kernel.org/

             reply	other threads:[~2025-01-25 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 22:22 Reiterer, Horst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-24 23:05 Regression: smb: chmod ignored (5.14.0-427.40.1.el9_4 vs. 5.14.0-503.15.1.el9_5) Reiterer, Horst
2025-01-24 23:16 ` Steve French
2025-01-25 14:25 ` Paulo Alcantara

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=e70df2a91d1346fdbe88463d4edbf05c@fabasoft.com \
    --to=horst.reiterer@fabasoft.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pc@manguebit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.