From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: Martin Doucha <martin.doucha@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] lib: tst_fd: Avoid tst_brk(TCONF, ...) on older distros
Date: Wed, 24 Jan 2024 15:56:32 +0100 [thread overview]
Message-ID: <20240124145632.GA307120@pevik> (raw)
In-Reply-To: <3d81343b-4e46-440e-99d6-c9870866ca86@suse.cz>
Hi Martin, Cyril,
> On 24. 01. 24 15:21, Cyril Hrubis wrote:
> > Hi!
> > > Actually at least here tst_syscall() needs to be called or it fails on older
> > > distros due missing ENOSYS check in raw syscall():
> > Ah, no we have to handle the ENOSYS ourselves as we do in the other
> > cases. Sorry for not realizing that.
> > We likely need just:
> > diff --git a/lib/tst_fd.c b/lib/tst_fd.c
> > index ab7de81aa..8b26ff8e5 100644
> > --- a/lib/tst_fd.c
> > +++ b/lib/tst_fd.c
> > @@ -141,7 +141,7 @@ static void open_pidfd(struct tst_fd *fd)
> > {
> > fd->fd = syscall(__NR_pidfd_open, getpid(), 0);
> > if (fd->fd < 0)
> > - tst_brk(TBROK | TERRNO, "pidfd_open()");
> > + tst_res(TCONF | TERRNO, "pidfd_open()");
> > }
Actually, the solution I posted [1] works on both old (affected) kernel and new
one:
- fd->fd = syscall(__NR_pidfd_open, getpid(), 0);
+ fd->fd = tst_syscall(__NR_pidfd_open, getpid(), 0);
if (fd->fd < 0)
tst_brk(TBROK | TERRNO, "pidfd_open()");
I guess we should merge your solution (otherwise we would need to change other
cases to be consistent), but I'm a bit confused. Is it the reason why we use
syscall() + tst_res(TCONF) instead of tst_syscall() + tst_brk(TBROK) that for
some cases it's expected to fail, thus TBROK is not accepted? Again, I was blind
when doing review.
If yes, please just go ahead and merge it.
Kind regards,
Petr
[1] https://lore.kernel.org/ltp/20240124142108.303782-1-pvorel@suse.cz/
> Yes, this will work. I missed the TBROK because I didn't look too closely at
> the unchanged lines in the patch...
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-24 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 12:58 [LTP] [PATCH] lib: tst_fd: Avoid tst_brk(TCONF, ...) on older distros Cyril Hrubis
2024-01-24 13:54 ` Martin Doucha
2024-01-24 14:10 ` Petr Vorel
2024-01-24 14:11 ` Cyril Hrubis
2024-01-24 14:22 ` Petr Vorel
2024-01-24 14:16 ` Petr Vorel
2024-01-24 14:21 ` Cyril Hrubis
2024-01-24 14:25 ` Petr Vorel
2024-01-24 14:36 ` Martin Doucha
2024-01-24 14:56 ` Petr Vorel [this message]
2024-01-24 15:19 ` Cyril Hrubis
2024-01-24 15:50 ` Petr Vorel
2024-01-24 16:57 ` Petr Vorel
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=20240124145632.GA307120@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.com \
--cc=mdoucha@suse.cz \
/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