mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Dionne <marc.dionne@auristor.com>
To: David Howells <dhowells@redhat.com>
Cc: Markus Suvanto <markus.suvanto@gmail.com>,
	Christian Brauner <brauner@kernel.org>,
	 linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] afs: Fix endless loop in directory parsing
Date: Fri, 23 Feb 2024 09:28:28 -0400	[thread overview]
Message-ID: <CAB9dFdvDitrof7a4Df1ziJJHnfqNModR7ZxBD971VCZuxyiEZQ@mail.gmail.com> (raw)
In-Reply-To: <786185.1708694102@warthog.procyon.org.uk>

On Fri, Feb 23, 2024 at 9:15 AM David Howells <dhowells@redhat.com> wrote:
>
>
> If a directory has a block with only ".__afsXXXX" files in it (from
> uncompleted silly-rename), these .__afsXXXX files are skipped but without
> advancing the file position in the dir_context.  This leads to
> afs_dir_iterate() repeating the block again and again.
>
> Fix this by making the code that skips the .__afsXXXX file also manually
> advance the file position.
>
> The symptoms are a soft lookup:
>
>         watchdog: BUG: soft lockup - CPU#3 stuck for 52s! [check:5737]
>         ...
>         RIP: 0010:afs_dir_iterate_block+0x39/0x1fd
>         ...
>          ? watchdog_timer_fn+0x1a6/0x213
>         ...
>          ? asm_sysvec_apic_timer_interrupt+0x16/0x20
>          ? afs_dir_iterate_block+0x39/0x1fd
>          afs_dir_iterate+0x10a/0x148
>          afs_readdir+0x30/0x4a
>          iterate_dir+0x93/0xd3
>          __do_sys_getdents64+0x6b/0xd4
>
> This is almost certainly the actual fix for:
>
>         https://bugzilla.kernel.org/show_bug.cgi?id=218496
>
> Fixes: 57e9d49c5452 ("afs: Hide silly-rename files from userspace")
> Signed-off-by: David Howells <dhowells@redhat.com>
> cc: Marc Dionne <marc.dionne@auristor.com>
> cc: Markus Suvanto <markus.suvanto@gmail.com>
> cc: linux-afs@lists.infradead.org
> ---
>  fs/afs/dir.c |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/afs/dir.c b/fs/afs/dir.c
> index b5b8de521f99..8a67fc427e74 100644
> --- a/fs/afs/dir.c
> +++ b/fs/afs/dir.c
> @@ -479,8 +479,10 @@ static int afs_dir_iterate_block(struct afs_vnode *dvnode,
>                     dire->u.name[0] == '.' &&
>                     ctx->actor != afs_lookup_filldir &&
>                     ctx->actor != afs_lookup_one_filldir &&
> -                   memcmp(dire->u.name, ".__afs", 6) == 0)
> +                   memcmp(dire->u.name, ".__afs", 6) == 0) {
> +                       ctx->pos = blkoff + next * sizeof(union afs_xdr_dirent);
>                         continue;
> +               }
>
>                 /* found the next entry */
>                 if (!dir_emit(ctx, dire->u.name, nlen,

Reviewed-by: Marc Dionne <marc.dionne@auristor.com>

Marc

  reply	other threads:[~2024-02-23 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 13:15 David Howells
2024-02-23 13:28 ` Marc Dionne [this message]
2024-02-23 15:15 ` Christian Brauner

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=CAB9dFdvDitrof7a4Df1ziJJHnfqNModR7ZxBD971VCZuxyiEZQ@mail.gmail.com \
    --to=marc.dionne@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=markus.suvanto@gmail.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 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®