From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it, Andrea Cervesato <andrea.cervesato@suse.com>
Subject: Re: [LTP] [PATCH 1/1] aiocp.c: TCONF on O_DIRECT on tmpfs
Date: Fri, 16 Dec 2022 14:13:39 +0100 [thread overview]
Message-ID: <Y5xvA6FvHtzrK6kU@pevik> (raw)
In-Reply-To: <Y5xt5K1HWp8lHau8@pevik>
> hm, it looks like it requires to skip tmpfs, as all tests TCONF:
> aiocp.c:231: TINFO: Maximum AIO blocks: 65536
> tst_device.c:541: TINFO: Use BTRFS specific strategy
> tst_device.c:559: TBROK: BTRFS ioctl failed. Is . on a tmpfs?: ENOTTY (25)
> I check if it'd work without
> e1b1ae66b2 ("tst_find_backing_dev: Get dev name from /sys/dev/block/*/uevent")
TMPDIR=/home/foo ./aiocp -b 1k -n 1 -f DIRECT # xfs
tst_test.c:1558: TINFO: Timeout per run is 0h 30m 30s
tst_test.c:1310: TINFO: xfs is supported by the test
aiocp.c:231: TINFO: Maximum AIO blocks: 65536
tst_device.c:585: TINFO: Use uevent strategy
aiocp.c:267: TINFO: Fill srcfile.bin with random data
aiocp.c:84: TBROK: write(3,0x7ffeccb9da00,60274) failed: EINVAL (22)
TMPDIR=/var/tmp ./aiocp -b 1k -n 1 -f DIRECT # ext4
tst_test.c:1558: TINFO: Timeout per run is 0h 30m 30s
tst_test.c:1310: TINFO: ext2/ext3/ext4 is supported by the test
aiocp.c:231: TINFO: Maximum AIO blocks: 65536
tst_device.c:585: TINFO: Use uevent strategy
aiocp.c:267: TINFO: Fill srcfile.bin with random data
aiocp.c:84: TBROK: write(3,0x7ffda9e14120,50530) failed: EINVAL (22)
uname -r
6.1.0-rc8-2.g2fb1790-default
=> even more things to investigate.
Kind regards,
Petr
> Kind regards,
> Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-12-16 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 11:50 [LTP] [PATCH 1/1] aiocp.c: TCONF on O_DIRECT on tmpfs Petr Vorel
2022-12-16 13:08 ` Petr Vorel
2022-12-16 13:13 ` Petr Vorel [this message]
2022-12-19 12:07 ` Cyril Hrubis
2022-12-23 18:26 ` Petr Vorel
2023-01-09 11:19 ` Richard Palethorpe
2022-12-20 13:19 ` Richard Palethorpe
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=Y5xvA6FvHtzrK6kU@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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