From: Chet Ramey <chet.ramey@case.edu>
To: Jeffrey E Altman <jaltman@auristor.com>,
David Howells <dhowells@redhat.com>
Cc: chet.ramey@case.edu, Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Etienne Champetier <champetier.etienne@gmail.com>,
Marc Dionne <marc.dionne@auristor.com>,
Steve French <sfrench@samba.org>,
linux-afs@lists.infradead.org, openafs-devel@openafs.org,
linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir
Date: Wed, 30 Apr 2025 14:36:37 -0400 [thread overview]
Message-ID: <b548ee65-3a54-43d7-aa6d-36e31cbf16f9@case.edu> (raw)
In-Reply-To: <8f6bd09c-c3d8-4142-938a-3fab5df7bd64@auristor.com>
On 4/30/25 1:26 PM, Jeffrey E Altman wrote:
> On 4/30/2025 12:14 PM, David Howells wrote:
>> Chet Ramey <chet.ramey@case.edu> wrote:
>>
>>> Well, except for CMU's report.
>> Do you know of any link for that? I'm guessing that is it was 1992,
>> there may
>> be no online record of it.
>>
>> David
>
> https://groups.google.com/g/gnu.bash.bug/c/6PPTfOgFdL4/m/2AQU-S1N76UJ?hl=en
Which of course just claims they reported it, but doesn't include the
report itself.
But Jeffrey's message seems to indicate that IBM addressed this particular
issue in AFS 3.2.
--
``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/
next prev parent reply other threads:[~2025-04-30 18:41 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 [this message]
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
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=b548ee65-3a54-43d7-aa6d-36e31cbf16f9@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