From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/ioctl_loop05: Use correct blockdev to get logical_block_size
Date: Wed, 10 Jun 2020 06:13:29 -0400 (EDT) [thread overview]
Message-ID: <1904123764.15455071.1591784009893.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1591767427-29383-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
----- Original Message -----
>
> Using df cmd (df -T /tmp/xxxxx/test.img)to get the correct block dev.
What I had in mind was to take "df -T" as inspiration, not call it directly,
but that could work too. See notes below.
> +static void find_backing_bdpath(char *buf)
> +{
> + char line[PATH_MAX];
> + FILE *file;
> +
> + file = SAFE_FOPEN("1.txt", "r");
> +
> + while (fgets(line, sizeof(line), file) != NULL)
> + sscanf(line, "%s", buf);
This will take the last line of output, which can be a problem as some
version align output differently. For example:
# df -T .
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/mapper/vg_dhcp13579-lv_root
ext4 46967160 3102232 41472456 7% /
can break output into two lines.
> + SAFE_FCLOSE(file);
> +}
> +
> static void setup(void)
> {
> - int fd;
> - struct stat buf;
> + char buf[100];
> + const char *const df_cmd[] = {"df", "-T", ".", NULL};
>
> if (tst_fs_type(".") == TST_TMPFS_MAGIC)
> tst_brk(TCONF, "tmpfd doesn't support O_DIRECT flag");
> @@ -109,13 +122,6 @@ static void setup(void)
> sprintf(sys_loop_diopath, "/sys/block/loop%d/loop/dio", dev_num);
> tst_fill_file("test.img", 0, 1024, 1024);
>
> - fd = SAFE_OPEN("test.img", O_RDONLY);
> - SAFE_FSTAT(fd, &buf);
> - SAFE_CLOSE(fd);
> -
> - logical_block_size = buf.st_blksize;
> - tst_res(TINFO, "backing dev logical_block_size is %d", logical_block_size);
> -
> tst_attach_device(dev_path, "test.img");
> attach_flag = 1;
> dev_fd = SAFE_OPEN(dev_path, O_RDWR);
> @@ -130,13 +136,24 @@ static void setup(void)
> * size of loop is bigger than the backing device's and the loop
> * needn't transform transfer.
> */
> - TST_RETRY_FUNC(ioctl(dev_fd, LOOP_SET_BLOCK_SIZE, logical_block_size),
> TST_RETVAL_EQ0);
> + SAFE_CMD(df_cmd, "1.txt", NULL);
This could be part of find_backing_bdpath() function.
What I had in mind when I referred to df was something like:
stat("test.img", &statbuf);
SAFE_MKNOD("blkdev", S_IFBLK | S_IRWXU, statbuf.st_dev);
block_devfd = SAFE_OPEN("blkdev", O_RDWR);
What do you think?
next prev parent reply other threads:[~2020-06-10 10:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 8:33 [LTP] [PATCH] syscalls/ioctl_loop05: Get the logic_block_size dynamically Yang Xu
2020-06-09 9:24 ` Jan Stancek
2020-06-09 9:48 ` Yang Xu
2020-06-09 10:16 ` Jan Stancek
2020-06-09 10:46 ` Yang Xu
2020-06-09 11:01 ` Jan Stancek
2020-06-10 1:19 ` Yang Xu
2020-06-10 5:37 ` [LTP] [PATCH v2] syscalls/ioctl_loop05: Use correct blockdev to get logical_block_size Yang Xu
2020-06-10 10:13 ` Jan Stancek [this message]
2020-06-10 10:42 ` Yang Xu
2020-06-10 12:19 ` Yang Xu
2020-06-10 13:04 ` Jan Stancek
2020-06-11 4:56 ` Yang Xu
2020-06-11 5:32 ` [LTP] [PATCH v3] " Yang Xu
2020-06-11 11:09 ` Jan Stancek
2020-06-12 2:57 ` Yang Xu
2020-06-24 5:07 ` Yang Xu
2020-06-24 11:32 ` Cyril Hrubis
2020-06-24 13:06 ` Jan Stancek
2020-06-25 17:10 ` Yang Xu
2020-06-28 7:42 ` [LTP] [PATCH v4 1/2] tst_device: Add new api tst_find_backing_dev(path, dev) Yang Xu
2020-06-28 7:42 ` [LTP] [PATCH v4 2/2] syscalls/ioctl_loop05: Use correct blockdev to get logical_block_size Yang Xu
2020-06-29 7:56 ` [LTP] [PATCH v4 1/2] tst_device: Add new api tst_find_backing_dev(path, dev) Jan Stancek
2020-06-29 10:37 ` Yang Xu
2020-06-29 11:08 ` Jan Stancek
2020-06-29 11:41 ` [LTP] [PATCH v5 " Yang Xu
2020-06-29 11:41 ` [LTP] [PATCH v5 2/2] syscalls/ioctl_loop05: Use correct blockdev to get logical_block_size Yang Xu
2020-07-02 9:18 ` [LTP] [PATCH v5 1/2] tst_device: Add new api tst_find_backing_dev(path, dev) Jan Stancek
2020-07-02 12:27 ` Cyril Hrubis
2020-07-02 13:17 ` Jan Stancek
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=1904123764.15455071.1591784009893.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.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