From: Lee Jones <lee@kernel.org>
To: Murphy Zhou <jencce.kernel@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] readahead01: pass on pidfd
Date: Wed, 15 May 2024 14:21:51 +0100 [thread overview]
Message-ID: <20240515132151.GA557949@google.com> (raw)
In-Reply-To: <20240423070643.38577-1-jencce.kernel@gmail.com>
On Tue, 23 Apr 2024, Murphy Zhou wrote:
> Linux kernel added pidfs via commit b5683a37c881 in v6.9-rc1
> release. This patchset ignores readahead request instead of
> returning EINVAL, so mark the test pass.
>
> https://lkml.iu.edu/hypermail/linux/kernel/2403.2/00762.html
>
> Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
> ---
> testcases/kernel/syscalls/readahead/readahead01.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/testcases/kernel/syscalls/readahead/readahead01.c b/testcases/kernel/syscalls/readahead/readahead01.c
> index d4b3f306f..aed8e7f31 100644
> --- a/testcases/kernel/syscalls/readahead/readahead01.c
> +++ b/testcases/kernel/syscalls/readahead/readahead01.c
> @@ -53,6 +53,7 @@ static void test_invalid_fd(struct tst_fd *fd)
> case TST_FD_MEMFD:
> case TST_FD_MEMFD_SECRET:
> case TST_FD_PROC_MAPS:
> + case TST_FD_PIDFD:
> return;
> default:
> break;
Any movement on this?
Android pre-submit CI testing is failing due to the new unconditional
enable of PIDFD. I believe this patch is required in order to bring it
back to a passing state.
--
Lee Jones [李琼斯]
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-05-15 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 7:06 [LTP] [PATCH] readahead01: pass on pidfd Murphy Zhou
2024-04-23 13:54 ` Petr Vorel
2024-04-24 0:28 ` Murphy Zhou
2024-05-15 13:21 ` Lee Jones [this message]
2024-05-15 13:40 ` Petr Vorel
2024-05-15 13:45 ` Cyril Hrubis
2024-05-15 13:52 ` Cyril Hrubis
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=20240515132151.GA557949@google.com \
--to=lee@kernel.org \
--cc=jencce.kernel@gmail.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