From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-unionfs@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Christian Brauner <brauner@kernel.org>, Zorro Lang <zlang@redhat.com>
Subject: Re: [PATCH] ovl: disable IOCB_DIO_CALLER_COMP
Date: Mon, 25 Sep 2023 11:38:03 +0200 [thread overview]
Message-ID: <20230925-perfide-enzianblau-5f6059909fd2@brauner> (raw)
In-Reply-To: <71897125-e570-46ce-946a-d4729725e28f@kernel.dk>
On Mon, 25 Sep 2023 00:21:35 -0600, Jens Axboe wrote:
> overlayfs copies the kiocb flags when it sets up a new kiocb to handle
> a write, but it doesn't properly support dealing with the deferred
> caller completions of the kiocb. This means it doesn't get the final
> write completion value, and hence will complete the write with '0' as
> the result.
>
> We could support the caller completions in overlayfs, but for now let's
> just disable them in the generated write kiocb.
>
> [...]
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes 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.fixes
[1/1] ovl: disable IOCB_DIO_CALLER_COMP
https://git.kernel.org/vfs/vfs/c/2d1b3bbc3dd5
next prev parent reply other threads:[~2023-09-25 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 6:21 Jens Axboe
2023-09-25 9:18 ` Amir Goldstein
2023-09-25 9:35 ` Jens Axboe
2023-09-25 9:39 ` Christian Brauner
2023-09-25 9:51 ` Jens Axboe
2023-09-25 9:38 ` Christian Brauner [this message]
2023-09-26 15:23 ` Zorro Lang
2023-09-26 15:31 ` Jens Axboe
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=20230925-perfide-enzianblau-5f6059909fd2@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=zlang@redhat.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®