From: Jens Axboe <axboe@kernel.dk>
To: Andres Freund <andres@anarazel.de>
Cc: "Dave Chinner" <david@fromorbit.com>,
"Theodore Ts'o" <tytso@mit.edu>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
"Shreeya Patel" <shreeya.patel@collabora.com>,
linux-ext4@vger.kernel.org,
"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
gustavo.padovan@collabora.com, zsm@google.com,
garrick@google.com,
"Linux regressions mailing list" <regressions@lists.linux.dev>,
io-uring@vger.kernel.org
Subject: Re: task hung in ext4_fallocate #2
Date: Wed, 25 Oct 2023 09:36:01 -0600 [thread overview]
Message-ID: <b5578447-81f6-4207-b83d-812da7c981a5@kernel.dk> (raw)
In-Reply-To: <20231025153135.kfnldzle3rglmfvp@awork3.anarazel.de>
On 10/25/23 9:31 AM, Andres Freund wrote:
> Hi,
>
> On 2023-10-24 18:34:05 -0600, Jens Axboe wrote:
>> Yeah I'm going to do a revert of the io_uring side, which effectively
>> disables it. Then a revised series can be done, and when done, we could
>> bring it back.
>
> I'm queueing a test to confirm that the revert actually fixes things.
> Is there still benefit in testing your other patch in addition
> upstream?
Don't think there's much point to testing the quick hack, I believe it
should work. So testing the most recent revert is useful, though I also
fully expect that to work. And then we can test the re-enable once that
is sent out, I did prepare a series. But timing is obviously unfortunate
for that, as it'll miss 6.6 and now also 6.7 due to the report timing.
FWIW, I wrote a small test case which does seem to trigger it very fast,
as expected:
#define _GNU_SOURCE
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <string.h>
#include <liburing.h>
#define BS 4096
#define FSIZE (128 * 1024 * 1024UL)
static int set_file_size(int fd, off_t file_size)
{
off_t this_size;
char buf[BS];
int ret;
memset(buf, 0, BS);
this_size = 0;
while (this_size < file_size) {
ret = write(fd, buf, BS);
if (ret != BS) {
fprintf(stderr, "write ret %d\n", ret);
return 1;
}
this_size += BS;
}
fsync(fd);
posix_fadvise(fd, 0, file_size, POSIX_FADV_DONTNEED);
return 0;
}
int main(int argc, char *argv[])
{
struct io_uring_sqe *sqe;
struct io_uring_cqe *cqe;
struct io_uring ring;
off_t off, foff;
int fd, i, ret;
void *buf;
if (argc < 2) {
fprintf(stderr, "%s <file>\n", argv[0]);
return 1;
}
fd = open(argv[1], O_RDWR | O_CREAT | O_TRUNC | O_DIRECT, 0644);
if (fd < 0) {
perror("open");
return 1;
}
if (set_file_size(fd, FSIZE))
return 1;
if (posix_memalign(&buf, 4096, BS))
return 1;
io_uring_queue_init(8, &ring, 0);
i = 0;
off = 0;
foff = FSIZE + BS;
do {
sqe = io_uring_get_sqe(&ring);
io_uring_prep_write(sqe, fd, buf, BS, off);
off += BS;
if (off == FSIZE)
off = 0;
io_uring_submit(&ring);
ret = posix_fallocate(fd, 0, foff);
if (ret < 0) {
perror("fallocate");
return 1;
}
foff += BS;
ret = io_uring_wait_cqe(&ring, &cqe);
if (ret) {
fprintf(stderr, "wait cqe %d\n", ret);
return 1;
}
io_uring_cqe_seen(&ring, cqe);
i++;
if (!(i & 1023))
fprintf(stdout, "Loop iteration %d\n", i);
} while (1);
return 0;
}
--
Jens Axboe
next prev parent reply other threads:[~2023-10-25 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 3:37 task hung in ext4_fallocate #2 Andres Freund
2023-10-18 0:43 ` Theodore Ts'o
2023-10-18 2:50 ` Andres Freund
2023-10-18 9:41 ` Andres Freund
2023-10-24 1:12 ` Dave Chinner
2023-10-24 1:36 ` Andres Freund
2023-10-24 14:30 ` Jens Axboe
2023-10-24 18:35 ` Jens Axboe
2023-10-25 0:06 ` Dave Chinner
2023-10-25 0:34 ` Jens Axboe
2023-10-25 15:31 ` Andres Freund
2023-10-25 15:36 ` Jens Axboe [this message]
2023-10-25 16:14 ` Andres Freund
2023-10-26 2:48 ` Andres Freund
2023-10-25 19:55 ` Theodore Ts'o
2023-10-25 22:28 ` Dave Chinner
2023-10-20 7:01 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-10-29 6:28 ` Linux regression tracking #update (Thorsten Leemhuis)
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=b5578447-81f6-4207-b83d-812da7c981a5@kernel.dk \
--to=axboe@kernel.dk \
--cc=andres@anarazel.de \
--cc=david@fromorbit.com \
--cc=garrick@google.com \
--cc=gustavo.padovan@collabora.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=ricardo.canuelo@collabora.com \
--cc=shreeya.patel@collabora.com \
--cc=tytso@mit.edu \
--cc=zsm@google.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