[OpenAFS-devel] Re: [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a
sticky dir
Chet Ramey
chet.ramey@case.edu
Wed, 14 May 2025 08:50:47 -0400
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------L5LSTY5M39gWnvMqVGp47caB
Content-Type: multipart/mixed; boundary="------------frKCS23FeCmgMLcTNF0WGjn4";
protected-headers="v1"
From: Chet Ramey <chet.ramey@case.edu>
Reply-To: 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>
Message-ID: <ad62849c-1728-4bae-b0d5-7d87dc94825f@case.edu>
Subject: Re: [PATCH] afs, bash: Fix open(O_CREAT) on an extant AFS file in a
sticky dir
References: <433928.1745944651@warthog.procyon.org.uk>
<20250505-erproben-zeltlager-4c16f07b96ae@brauner>
<CAOdf3grbDQ-Fh2bV7XfoYvVBhgBAh7-hZyyxTNt1RfGekrA-nA@mail.gmail.com>
<66c958db-0408-451d-b362-fed1f56d7c6d@auristor.com>
In-Reply-To: <66c958db-0408-451d-b362-fed1f56d7c6d@auristor.com>
--------------frKCS23FeCmgMLcTNF0WGjn4
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64
T24gNS81LzI1IDEwOjQyIEFNLCBKZWZmcmV5IEUgQWx0bWFuIHdyb3RlOg0KDQo+Pj4gU28g
dGhlbiBqdXN0IGRvbid0IHJlbW92ZSBpdC4gSSBkb24ndCBzZWUgYSByZWFzb24gZm9yIHVz
IHRvIHdvcmthcm91bmQNCj4+PiB1c2Vyc3BhY2UgY3JlYXRpbmcgYSBidWcgZm9yIGl0c2Vs
ZiBhbmQgZm9yY2luZyB1cyB0byBhZGQgdHdvIG5ldyBpbm9kZQ0KPj4+IG9wZXJhdGlvbnMg
dG8gd29yayBhcm91bmQgaXQuDQo+PiBUaGlzIGJhc2ggd29ya2Fyb3VuZCBpbnRyb2R1Y2Vk
IGFnZXMgYWdvIGZvciBBRlMgYnlwYXNzIGZzLnByb3RlY3RlZF9yZWd1bGFyDQo+IA0KPiBD
aGV0LCBJIGRvbid0IHRoaW5rIHRoaXMgaGlzdG9yeSBpcyBjb3JyZWN0LiANCg0KSSB0aGlu
ayBFdGllbm5lJ3MgdGVyc2UgY29tbWVudCBhY2N1cmF0ZWx5IHN1bW1hcml6ZXMgdGhlIGN1
cnJlbnQgcHJvYmxlbQ0KKGFuZCBtYXliZSBpdCB3b3VsZCByZWFkIG1vcmUgY2xlYXJseSBp
ZiBoZSBoYWQgdXNlZCBgYnlwYXNzZXMnKS4NCg0KLS0gDQpgYFRoZSBseWYgc28gc2hvcnQs
IHRoZSBjcmFmdCBzbyBsb25nIHRvIGxlcm5lLicnIC0gQ2hhdWNlcg0KCQkgYGBBcnMgbG9u
Z2EsIHZpdGEgYnJldmlzJycgLSBIaXBwb2NyYXRlcw0KQ2hldCBSYW1leSwgVVRlY2gsIENX
UlUgICAgY2hldEBjYXNlLmVkdSAgICBodHRwOi8vdGlzd3d3LmN3cnUuZWR1L35jaGV0Lw0K
--------------frKCS23FeCmgMLcTNF0WGjn4--
--------------L5LSTY5M39gWnvMqVGp47caB
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature.asc"
-----BEGIN PGP SIGNATURE-----
wmMEABEIACMWIQR8ATX7CIqvbGbGULm7WGnwZOp0qwUCaCSRpwUDAAAAAAAKCRC7WGnwZOp0q8F+
AJ9LqPEdLlhWqcMgSVEfvfVvQQaLUQCeJ3uT3ggHKj9klGbE8GZKsHHVarM=
=1TNa
-----END PGP SIGNATURE-----
--------------L5LSTY5M39gWnvMqVGp47caB--