mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Marc Dionne <marc.dionne@auristor.com>,
	David Howells <dhowells@redhat.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: Fix the fallback handling for the YFS.RemoveFile2 RPC call
Date: Wed, 15 Jan 2025 11:47:36 +0100	[thread overview]
Message-ID: <20250115-gepfiffen-wenig-799588d55bb5@brauner> (raw)
In-Reply-To: <109541.1736865963@warthog.procyon.org.uk>

On Tue, 14 Jan 2025 14:46:03 +0000, David Howells wrote:
> Fix a pair of bugs in the fallback handling for the YFS.RemoveFile2 RPC
> call:
> 
>  (1) Fix the abort code check to also look for RXGEN_OPCODE.  The lack of
>      this masks the second bug.
> 
>  (2) call->server is now not used for ordinary filesystem RPC calls that
>      have an operation descriptor.  Fix to use call->op->server instead.
> 
> [...]

Applied to the vfs-6.14.afs branch of the vfs/vfs.git tree.
Patches in the vfs-6.14.afs branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.14.afs

[1/1] afs: Fix the fallback handling for the YFS.RemoveFile2 RPC call
      https://git.kernel.org/vfs/vfs/c/e30458d690f3

      reply	other threads:[~2025-01-15 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 14:46 David Howells
2025-01-15 10:47 ` Christian Brauner [this message]

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=20250115-gepfiffen-wenig-799588d55bb5@brauner \
    --to=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 \
    /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®