From: Jens Axboe <axboe@kernel.dk>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Jann Horn <jannh@google.com>,
linux-bcachefs@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
Pavel Begunkov <asml.silence@gmail.com>,
io-uring <io-uring@vger.kernel.org>
Subject: Re: bcachefs: suspicious mm pointer in struct dio_write
Date: Wed, 27 Nov 2024 14:59:17 -0700 [thread overview]
Message-ID: <97465113-ea1a-4cee-9235-d6900158aa74@kernel.dk> (raw)
In-Reply-To: <hrx6kaqeyqdchmv24xivrooyimackqx5mxm6vlvj3y5gusxgno@gjsbtm76unrs>
On 11/27/24 2:58 PM, Kent Overstreet wrote:
>>> By the way, did the lifetime issue that was causing umount/remount to
>>> fail ever get resolved? I've currently got no test coverage for
>>> io_uring, would be nice to flip that back on.
>>
>> Nope, I do have an updated branch since then, but it's still sitting
>> waiting on getting a bit more love. I suspect it'll be done for 6.14.
>
> Alright - if you want to ping me when that's ready, along with any other
> knobs I should flip on for io_uring support, I'll flip io_uring back on
> in my test infrastructure at that time.
Will do, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2024-11-27 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 16:57 bcachefs: suspicious mm pointer in struct dio_write Jann Horn
2024-11-27 18:09 ` Jens Axboe
2024-11-27 19:43 ` Jann Horn
2024-11-27 20:01 ` Jens Axboe
2024-11-27 20:31 ` Kent Overstreet
2024-11-27 20:25 ` Kent Overstreet
2024-11-27 20:44 ` Jann Horn
2024-11-27 21:08 ` Kent Overstreet
2024-11-27 21:16 ` Jens Axboe
2024-11-27 21:27 ` Kent Overstreet
2024-11-27 21:51 ` Jens Axboe
2024-11-27 21:58 ` Kent Overstreet
2024-11-27 21:59 ` Jens Axboe [this message]
2024-11-27 21:39 ` Jann Horn
2024-11-27 21:52 ` Jens Axboe
2024-11-27 21:53 ` Jann Horn
2024-11-27 20:23 ` Kent Overstreet
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=97465113-ea1a-4cee-9235-d6900158aa74@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=jannh@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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