LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Nadav Amit <nadav.amit@gmail.com> To: Jens Axboe <axboe@kernel.dk> Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org, Nadav Amit <namit@vmware.com>, Pavel Begunkov <asml.silence@gmail.com> Subject: [PATCH 0/2] io_uring: bug fixes Date: Sat, 7 Aug 2021 17:13:40 -0700 [thread overview] Message-ID: <20210808001342.964634-1-namit@vmware.com> (raw) From: Nadav Amit <namit@vmware.com> Two small bug fixes. The first fix is for a real issue that encountered on 5.13, which caused my workload not to work with a submission queue. Apparently, on 5.14 it is only a performance issue (i.e., not a functionality issue). The second fix is for a theoretical issue. I did not cc stable, as I leave this decision to the maintainer. Cc: Jens Axboe <axboe@kernel.dk> Cc: Pavel Begunkov <asml.silence@gmail.com> Nadav Amit (2): io_uring: clear TIF_NOTIFY_SIGNAL when running task work io_uring: Use WRITE_ONCE() when writing to sq_flags fs/io_uring.c | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) -- 2.25.1
next reply other threads:[~2021-08-08 0:14 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-08 0:13 Nadav Amit [this message] 2021-08-08 0:13 ` [PATCH 1/2] io_uring: clear TIF_NOTIFY_SIGNAL when running task work Nadav Amit 2021-08-08 12:55 ` Pavel Begunkov 2021-08-08 17:31 ` Nadav Amit 2021-08-09 4:07 ` Hao Xu 2021-08-09 4:50 ` Nadav Amit 2021-08-09 10:35 ` Pavel Begunkov 2021-08-09 10:18 ` Pavel Begunkov 2021-08-09 21:48 ` Olivier Langlois 2021-08-10 8:28 ` Nadav Amit 2021-08-10 13:33 ` Olivier Langlois 2021-08-10 21:32 ` Pavel Begunkov 2021-08-11 2:33 ` Nadav Amit 2021-08-11 2:51 ` Jens Axboe 2021-08-11 5:40 ` I/O cancellation in io-uring (was: io_uring: clear TIF_NOTIFY_SIGNAL ...) Nadav Amit 2021-08-08 0:13 ` [PATCH 2/2] io_uring: Use WRITE_ONCE() when writing to sq_flags Nadav Amit 2021-08-09 13:53 ` [PATCH 0/2] io_uring: bug fixes 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=20210808001342.964634-1-namit@vmware.com \ --to=nadav.amit@gmail.com \ --cc=asml.silence@gmail.com \ --cc=axboe@kernel.dk \ --cc=io-uring@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=namit@vmware.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: linkBe 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; as well as URLs for NNTP newsgroup(s).