From: Timothy Pearson <tpearson@raptorengineering.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: regressions <regressions@lists.linux.dev>,
Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: Regression in io_uring, leading to data corruption
Date: Thu, 9 Nov 2023 11:00:41 -0600 (CST) [thread overview]
Message-ID: <1557819821.46044536.1699549241816.JavaMail.zimbra@raptorengineeringinc.com> (raw)
In-Reply-To: <9860f9b2-1d98-497c-9480-56852fda781b@kernel.dk>
----- Original Message -----
> From: "Jens Axboe" <axboe@kernel.dk>
> To: "Timothy Pearson" <tpearson@raptorengineering.com>
> Cc: "regressions" <regressions@lists.linux.dev>, "Pavel Begunkov" <asml.silence@gmail.com>
> Sent: Thursday, November 9, 2023 9:12:07 AM
> Subject: Re: Regression in io_uring, leading to data corruption
> On 11/8/23 4:58 PM, Jens Axboe wrote:
>> On 11/8/23 3:18 PM, Jens Axboe wrote:
>>> OK, let me actually test this thing and see if I can make it solid
>>> first...
>>
>> Here's a suitable hack - it just creates a new io worker for each item,
>> ensuring that that worker is run on the same CPU.
>
> Turns out I didn't send you the current one, this one was older and
> untested. Please try this one instead.
I'm still seeing an oops with this newer patchset applied:
[ 76.419788] Kernel attempted to read user page (9c) - exploit attempt? (uid: 0)
[ 76.419853] BUG: Kernel NULL pointer dereference on read at 0x0000009c
[ 76.419887] Faulting instruction address: 0xc0000000008374d4
[ 76.419919] Oops: Kernel access of bad area, sig: 11 [#1]
<snip>
[ 76.429125] Call Trace:
[ 76.429142] [c000000009a8f800] [c000000000ea4e7c] schedule+0xfc/0x150 (unreliable)
[ 76.429190] [c000000009a8f870] [c000000000ead8f0] schedule_timeout+0x170/0x1e0
[ 76.429238] [c000000009a8f940] [c000000000ea3fc8] io_schedule_timeout+0x68/0xa0
[ 76.429285] [c000000009a8f970] [c0000000007adcbc] blk_io_schedule+0x3c/0x70
[ 76.429326] [c000000009a8f990] [c00000000065da84] __iomap_dio_rw+0x8d4/0x9f0
[ 76.429374] [c000000009a8fb70] [c00000000065dea0] iomap_dio_rw+0x20/0x80
[ 76.429415] [c000000009a8fb90] [c008000000514eac] ext4_file_write_iter+0x814/0xdb8 [ext4]
[ 76.429475] [c000000009a8fc60] [c000000000833aa0] io_write+0x280/0x540
[ 76.429514] [c000000009a8fd80] [c0000000008183bc] io_issue_sqe+0xdc/0x390
[ 76.429554] [c000000009a8fdd0] [c000000000818ab4] io_wq_submit_work+0x1c4/0x2c0
[ 76.429601] [c000000009a8fe20] [c000000000835578] io_wq_single_worker+0x88/0xb0
[ 76.429652] [c000000009a8fe50] [c00000000000df3c] ret_from_kernel_user_thread+0x14/0x1c
If you're not seeing an oops, that's an interesting difference that I can investigate further.
next prev parent reply other threads:[~2023-11-09 17:00 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 16:34 Regression in io_uring, leading to data corruption Timothy Pearson
2023-11-07 16:49 ` Jens Axboe
2023-11-07 16:57 ` Timothy Pearson
2023-11-07 17:14 ` Jens Axboe
2023-11-07 21:22 ` Jens Axboe
2023-11-07 21:39 ` Timothy Pearson
2023-11-07 21:46 ` Jens Axboe
2023-11-07 22:07 ` Timothy Pearson
2023-11-07 22:16 ` Jens Axboe
2023-11-07 22:29 ` Timothy Pearson
2023-11-07 22:44 ` Jens Axboe
2023-11-07 23:12 ` Timothy Pearson
2023-11-07 23:16 ` Jens Axboe
2023-11-07 23:34 ` Timothy Pearson
2023-11-07 23:52 ` Jens Axboe
2023-11-08 0:02 ` Timothy Pearson
2023-11-08 0:09 ` Jens Axboe
2023-11-08 3:27 ` Timothy Pearson
2023-11-08 3:30 ` Timothy Pearson
2023-11-08 4:00 ` Timothy Pearson
2023-11-08 15:10 ` Jens Axboe
2023-11-08 15:14 ` Jens Axboe
2023-11-08 17:10 ` Timothy Pearson
2023-11-08 17:26 ` Jens Axboe
2023-11-08 17:40 ` Timothy Pearson
2023-11-08 17:49 ` Jens Axboe
2023-11-08 17:57 ` Jens Axboe
2023-11-08 18:36 ` Timothy Pearson
2023-11-08 18:51 ` Timothy Pearson
2023-11-08 19:08 ` Jens Axboe
2023-11-08 19:06 ` Jens Axboe
2023-11-08 22:05 ` Jens Axboe
2023-11-08 22:15 ` Timothy Pearson
2023-11-08 22:18 ` Jens Axboe
2023-11-08 22:28 ` Timothy Pearson
2023-11-08 23:58 ` Jens Axboe
2023-11-09 15:12 ` Jens Axboe
2023-11-09 17:00 ` Timothy Pearson [this message]
2023-11-09 17:17 ` Jens Axboe
2023-11-09 17:24 ` Timothy Pearson
2023-11-09 17:30 ` Jens Axboe
2023-11-09 17:36 ` Timothy Pearson
2023-11-09 17:38 ` Jens Axboe
2023-11-09 17:42 ` Timothy Pearson
2023-11-09 17:45 ` Jens Axboe
2023-11-09 18:20 ` tpearson
2023-11-10 3:51 ` Jens Axboe
2023-11-10 4:35 ` Timothy Pearson
2023-11-10 6:48 ` Timothy Pearson
2023-11-10 14:52 ` Jens Axboe
2023-11-11 18:42 ` Timothy Pearson
2023-11-11 18:58 ` Jens Axboe
2023-11-11 19:04 ` Timothy Pearson
2023-11-11 19:11 ` Jens Axboe
2023-11-11 19:15 ` Timothy Pearson
2023-11-11 19:23 ` Jens Axboe
2023-11-11 21:57 ` Timothy Pearson
2023-11-13 17:06 ` Timothy Pearson
2023-11-13 17:39 ` Jens Axboe
2023-11-13 19:02 ` Timothy Pearson
2023-11-13 19:29 ` Jens Axboe
2023-11-13 20:58 ` Timothy Pearson
2023-11-13 21:22 ` Timothy Pearson
2023-11-13 22:15 ` Jens Axboe
2023-11-13 23:19 ` Timothy Pearson
2023-11-13 23:48 ` Jens Axboe
2023-11-14 0:04 ` Timothy Pearson
2023-11-14 0:13 ` Jens Axboe
2023-11-14 0:52 ` Timothy Pearson
2023-11-14 5:06 ` Timothy Pearson
2023-11-14 13:17 ` Jens Axboe
2023-11-14 16:59 ` Timothy Pearson
2023-11-14 17:04 ` Jens Axboe
2023-11-14 17:14 ` Timothy Pearson
2023-11-14 17:17 ` Jens Axboe
2023-11-14 17:21 ` Timothy Pearson
2023-11-14 17:57 ` Timothy Pearson
2023-11-14 18:02 ` Jens Axboe
2023-11-14 18:12 ` Timothy Pearson
2023-11-14 18:26 ` Jens Axboe
2023-11-15 11:03 ` Timothy Pearson
2023-11-15 16:46 ` Jens Axboe
2023-11-15 17:03 ` Timothy Pearson
2023-11-15 18:30 ` Jens Axboe
2023-11-15 18:35 ` Timothy Pearson
2023-11-15 18:37 ` Jens Axboe
2023-11-15 18:40 ` Timothy Pearson
2023-11-15 19:00 ` Jens Axboe
2023-11-16 3:28 ` Timothy Pearson
2023-11-16 3:46 ` Jens Axboe
2023-11-16 3:54 ` Timothy Pearson
2023-11-19 0:16 ` Timothy Pearson
2023-11-13 20:47 ` Jens Axboe
2023-11-13 21:08 ` Timothy Pearson
2023-11-10 14:48 ` 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=1557819821.46044536.1699549241816.JavaMail.zimbra@raptorengineeringinc.com \
--to=tpearson@raptorengineering.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.