From: Cyril Hrubis <chrubis@suse.cz>
To: Reuben Hawkins <reubenhwk@gmail.com>
Cc: mszeredi@redhat.com, brauner@kernel.org, lkp@intel.com,
willy@infradead.org, oe-lkp@lists.linux.dev,
kernel test robot <oliver.sang@intel.com>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] vfs: fix readahead(2) on block devices
Date: Fri, 22 Sep 2023 11:10:20 +0200 [thread overview]
Message-ID: <ZQ1Z_JHMPE3hrzv5@yuki> (raw)
In-Reply-To: <CAD_8n+TpZF2GoE1HUeBLs0vmpSna0yR9b+hsd-VC1ZurTe41LQ@mail.gmail.com>
Hi!
> ack. Will try to test. My Ubuntu 22.04 system wasn't able to find
> packages called
> for by the test case, so it'll take me a little while to figure out how to
> get the
> test case working...
Huh? The test is a simple C binary you shouldn't need anything more
than:
$ git clone https://github.com/linux-test-project/ltp.git
$ cd ltp
$ make autotools
$ ./configure
$ cd testcases/kernel/syscalls/readahead
$ make
$ ./readahead01
And this is well described in the readme at:
https://github.com/linux-test-project/ltp/
And the packages required for the compilation are make, C compiler and
autotools nothing extraordinary.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Reuben Hawkins <reubenhwk@gmail.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
mszeredi@redhat.com, brauner@kernel.org, lkp@intel.com,
willy@infradead.org, linux-fsdevel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>,
viro@zeniv.linux.org.uk, oe-lkp@lists.linux.dev,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] vfs: fix readahead(2) on block devices
Date: Fri, 22 Sep 2023 11:10:20 +0200 [thread overview]
Message-ID: <ZQ1Z_JHMPE3hrzv5@yuki> (raw)
In-Reply-To: <CAD_8n+TpZF2GoE1HUeBLs0vmpSna0yR9b+hsd-VC1ZurTe41LQ@mail.gmail.com>
Hi!
> ack. Will try to test. My Ubuntu 22.04 system wasn't able to find
> packages called
> for by the test case, so it'll take me a little while to figure out how to
> get the
> test case working...
Huh? The test is a simple C binary you shouldn't need anything more
than:
$ git clone https://github.com/linux-test-project/ltp.git
$ cd ltp
$ make autotools
$ ./configure
$ cd testcases/kernel/syscalls/readahead
$ make
$ ./readahead01
And this is well described in the readme at:
https://github.com/linux-test-project/ltp/
And the packages required for the compilation are make, C compiler and
autotools nothing extraordinary.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2023-09-22 9:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 4:38 [PATCH] vfs: fix readahead(2) on block devices Reuben Hawkins
2023-09-09 6:36 ` Amir Goldstein
2023-09-10 10:02 ` Christian Brauner
2023-09-11 8:15 ` Amir Goldstein
2023-09-19 2:47 ` [LTP] " kernel test robot
2023-09-19 2:47 ` kernel test robot
2023-09-19 8:43 ` [LTP] " Amir Goldstein
2023-09-19 8:43 ` Amir Goldstein
2023-09-21 13:01 ` [LTP] " Reuben Hawkins
2023-09-21 14:44 ` Amir Goldstein
2023-09-21 14:44 ` Amir Goldstein
2023-09-22 9:10 ` Cyril Hrubis [this message]
2023-09-22 9:10 ` [LTP] " Cyril Hrubis
2023-09-22 20:29 ` Reuben Hawkins
2023-09-23 5:56 ` Amir Goldstein
2023-09-23 5:56 ` Amir Goldstein
2023-09-23 12:20 ` Reuben Hawkins
2023-09-23 12:28 ` Reuben Hawkins
2023-09-23 14:41 ` Matthew Wilcox
2023-09-23 14:41 ` Matthew Wilcox
2023-09-23 15:48 ` Amir Goldstein
2023-09-23 15:48 ` Amir Goldstein
2023-09-24 3:48 ` Reuben Hawkins
2023-09-24 6:46 ` Amir Goldstein
2023-09-24 6:46 ` Amir Goldstein
2023-09-24 11:47 ` Amir Goldstein
2023-09-24 11:47 ` Amir Goldstein
2023-09-24 14:27 ` Matthew Wilcox
2023-09-24 14:27 ` Matthew Wilcox
2023-09-24 15:32 ` Amir Goldstein
2023-09-24 15:32 ` Amir Goldstein
2023-09-24 21:56 ` Matthew Wilcox
2023-09-24 21:56 ` Matthew Wilcox
2023-09-25 4:35 ` Reuben Hawkins
2023-09-25 6:42 ` Matthew Wilcox
2023-09-25 6:42 ` Matthew Wilcox
2023-09-25 9:43 ` Amir Goldstein
2023-09-25 9:43 ` Amir Goldstein
2023-09-25 12:39 ` Christian Brauner
2023-09-25 12:39 ` Christian Brauner
2023-09-25 15:36 ` Reuben Hawkins
2023-09-25 16:51 ` Amir Goldstein
2023-09-25 16:51 ` Amir Goldstein
2023-09-26 10:08 ` Christian Brauner
2023-09-26 10:08 ` Christian Brauner
2023-09-26 1:56 ` Oliver Sang
2023-09-26 1:56 ` Oliver Sang
2023-09-26 5:34 ` Amir Goldstein
2023-09-26 5:34 ` Amir Goldstein
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=ZQ1Z_JHMPE3hrzv5@yuki \
--to=chrubis@suse.cz \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=mszeredi@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=reubenhwk@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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.