From: "Darrick J. Wong" <djwong@kernel.org>
To: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>
Subject: Re: [PATCH] src/t_ofd_locks.c: Reset errno to zero
Date: Mon, 15 Aug 2022 07:30:11 -0700 [thread overview]
Message-ID: <YvpYc6tHtgWIQAAF@magnolia> (raw)
In-Reply-To: <585a8c5d-81c5-c40a-b7c2-b50f36d6fb0c@fujitsu.com>
On Mon, Aug 15, 2022 at 10:06:59AM +0000, xuyang2018.jy@fujitsu.com wrote:
>
>
> on 2022/08/05 23:00, Darrick J. Wong wrote:
> > On Thu, Aug 04, 2022 at 02:18:52PM +0800, Yang Xu wrote:
> >> It seems I met libcap errno bug again when using libcap-2.48-4.el8.x86_64.
> >> But this time, errno is EINVAL if c program link with lcap.
> >> Lastest upstream libcap doesn't have bug and it should be backport bug.
> >>
> >> generic/478 will become not run because of this. To fix this that only
> >> exists on some distributions, reset errno to zero.
> >>
> >> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
> >> ---
> >> src/t_ofd_locks.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/src/t_ofd_locks.c b/src/t_ofd_locks.c
> >> index e3b15ddc..e77f2659 100644
> >> --- a/src/t_ofd_locks.c
> >> +++ b/src/t_ofd_locks.c
> >> @@ -187,6 +187,8 @@ int main(int argc, char **argv)
> >> struct sembuf sop;
> >> int opt, ret, retry;
> >>
> >> + //avoid libcap errno bug
> >> + errno = 0;
> >
> > What sets errno to EINVAL here? And what actually causes the program to
> > exit with code 22?
> >
> > There aren't any library calls prior to this point, right? Or is this
> > ... libpcap has some initcall that runs quietly in the background before
> > main starts, so we enter main with errno==EINVAL, which then causes ...
> > something else to break?
> Yes,
>
> #include <stdio.h>
> #include <errno.h>
> int main(int argc, char **argv)
> {
> printf("errno %d\n", errno);
> return 0;
> }
>
> gcc test.c -lcap -o test
>
> then run test, errno is EINVAL.
>
> But upstream libcap is ok and it should be a backport bug on libcap
> distribution version.
Yay for still paying for poor decisions of the 1970s in 2022...
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
>
> Best Regards
> Yang Xu
> >
> > --D
> >
> >> while((opt = getopt(argc, argv, "sgrwo:l:PRWtFd")) != -1) {
> >> switch(opt) {
> >> case 's':
> >> --
> >> 2.27.0
> >>
prev parent reply other threads:[~2022-08-15 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 6:18 [PATCH] src/t_ofd_locks.c: Reset errno to zero Yang Xu
2022-08-05 15:00 ` Darrick J. Wong
2022-08-15 10:06 ` xuyang2018.jy
2022-08-15 14:30 ` Darrick J. Wong [this message]
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=YvpYc6tHtgWIQAAF@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=xuyang2018.jy@fujitsu.com \
/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.