mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffrey E Altman <jaltman@auristor.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	David Howells <dhowells@redhat.com>,
	Marc Dionne <marc.dionne@auristor.com>,
	Markus Suvanto <markus.suvanto@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] afs: Revert "afs: Hide silly-rename files from userspace"
Date: Wed, 13 Mar 2024 11:20:59 -0400	[thread overview]
Message-ID: <2c15fb50-85ed-44fd-a93e-2083bea93ac5@auristor.com> (raw)
In-Reply-To: <544d7b9d-ef15-463f-a11c-9a3cca3a49ea@infradead.org>


[-- Attachment #1.1: Type: text/plain, Size: 779 bytes --]

On 3/13/2024 11:16 AM, Randy Dunlap wrote:
> On 3/13/24 04:08, David Howells wrote:
>>      
>> This reverts commit 57e9d49c54528c49b8bffe6d99d782ea051ea534.
>>
>> This undoes the hiding of .__afsXXXX silly-rename files.  The problem with
>> hiding them is that rm can't then manually delete them.
>>
>> This also reverts commit 5f7a07646655fb4108da527565dcdc80124b14c4 ("afs: Fix
>> endless loop in directory parsing") as that's a bugfix for the above.
>>
>> Fixes: 57e9d49c5452 ("afs: Hide silly-rename files from userspace")
>> Reported-by: Markus Suvanto<markus.suvanto@gmail.com>
>> Link:https://lists.infradead.org/pipermail/linux-afs/2024-February/008102html
> Not Found
>
> The requested URL was not found on this server.

The dot before the "html" extension is missing.

[-- Attachment #1.2: Type: text/html, Size: 1512 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4039 bytes --]

  reply	other threads:[~2024-03-13 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13 11:08 David Howells
2024-03-13 15:16 ` Randy Dunlap
2024-03-13 15:20   ` Jeffrey E Altman [this message]
2024-03-14 10:54 ` Christian Brauner
2024-03-14 10:55 ` David Howells
2024-03-14 14:24   ` Randy Dunlap
2024-03-14 12:47 ` Jeffrey E Altman

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=2c15fb50-85ed-44fd-a93e-2083bea93ac5@auristor.com \
    --to=jaltman@auristor.com \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=markus.suvanto@gmail.com \
    --cc=rdunlap@infradead.org \
    /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

all inboxes | Powered by JetHome®