From: Jens Axboe <[email protected]>
To: Joseph Qi <[email protected]>
Cc: [email protected], [email protected],
Heming Zhao <[email protected]>,
Xiaoguang Wang <[email protected]>
Subject: Re: [PATCH] io_uring: fix fget leak when fs don't support nowait buffered read
Date: Tue, 28 Feb 2023 05:59:31 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 28 Feb 2023 12:54:59 +0800, Joseph Qi wrote:
> Heming reported a BUG when using io_uring doing link-cp on ocfs2. [1]
>
> Do the following steps can reproduce this BUG:
> mount -t ocfs2 /dev/vdc /mnt/ocfs2
> cp testfile /mnt/ocfs2/
> ./link-cp /mnt/ocfs2/testfile /mnt/ocfs2/testfile.1
> umount /mnt/ocfs2
>
> [...]
Applied, thanks!
[1/1] io_uring: fix fget leak when fs don't support nowait buffered read
commit: 54aa7f2330b82884f4a1afce0220add6e8312f8b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-02-28 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 4:54 [PATCH] io_uring: fix fget leak when fs don't support nowait buffered read Joseph Qi
2023-02-28 12:59 ` Jens Axboe [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=167758917178.12826.13481934362166793957.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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