From: Chet Ramey <chet.ramey@case.edu>
To: Jeffrey E Altman <jaltman@auristor.com>,
Etienne Champetier <champetier.etienne@gmail.com>,
Christian Brauner <brauner@kernel.org>
Cc: chet.ramey@case.edu, David Howells <dhowells@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Marc Dionne <marc.dionne@auristor.com>,
Steve French <sfrench@samba.org>,
linux-fsdevel@vger.kernel.org,
Linux AFS mailing list <linux-afs@lists.infradead.org>,
linux-kernel@vger.kernel.org, linux-cifs@vger.kernel.org,
"openafs-devel@openafs.org" <openafs-devel@openafs.org>
Subject: Re: [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir
Date: Wed, 14 May 2025 08:50:47 -0400 [thread overview]
Message-ID: <ad62849c-1728-4bae-b0d5-7d87dc94825f@case.edu> (raw)
In-Reply-To: <66c958db-0408-451d-b362-fed1f56d7c6d@auristor.com>
[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]
On 5/5/25 10:42 AM, Jeffrey E Altman wrote:
>>> So then just don't remove it. I don't see a reason for us to workaround
>>> userspace creating a bug for itself and forcing us to add two new inode
>>> operations to work around it.
>> This bash workaround introduced ages ago for AFS bypass fs.protected_regular
>
> Chet, I don't think this history is correct.
I think Etienne's terse comment accurately summarizes the current problem
(and maybe it would read more clearly if he had used `bypasses').
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2025-05-14 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 16:37 [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir David Howells
2025-04-29 17:35 ` Jeffrey E Altman
2025-04-30 15:09 ` Chet Ramey
2025-04-30 16:14 ` David Howells
2025-04-30 17:26 ` Jeffrey E Altman
2025-04-30 18:36 ` Chet Ramey
2025-05-05 13:14 ` Christian Brauner
[not found] ` <CAOdf3grbDQ-Fh2bV7XfoYvVBhgBAh7-hZyyxTNt1RfGekrA-nA@mail.gmail.com>
2025-05-05 14:42 ` Jeffrey E Altman
2025-05-14 12:50 ` Chet Ramey [this message]
2025-05-06 10:26 ` David Howells
2025-05-09 10:33 ` Christian Brauner
2025-05-12 13:02 ` [PATCH v2] " David Howells
2025-05-13 7:49 ` Christian Brauner
2025-05-13 8:30 ` David Howells
2025-05-13 15:44 ` Jeffrey E Altman
2025-05-14 12:49 ` [PATCH] " Chet Ramey
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=ad62849c-1728-4bae-b0d5-7d87dc94825f@case.edu \
--to=chet.ramey@case.edu \
--cc=brauner@kernel.org \
--cc=champetier.etienne@gmail.com \
--cc=dhowells@redhat.com \
--cc=jaltman@auristor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=openafs-devel@openafs.org \
--cc=sfrench@samba.org \
--cc=viro@zeniv.linux.org.uk \
/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