All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, libc-alpha-help@sourceware.org
Subject: Re: [PATCH] generic/486: print correct errno
Date: Wed, 16 May 2018 08:27:14 -0700	[thread overview]
Message-ID: <20180516152714.GA4910@magnolia> (raw)
In-Reply-To: <1526457604-10060-1-git-send-email-yangx.jy@cn.fujitsu.com>

On Wed, May 16, 2018 at 04:00:04PM +0800, Xiao Yang wrote:
> On glibc v2.12 or v2.17, running generic/486 with XFS got wrong
> EINVAL instead of ENODATA:
> ----------------------------------------------------------------
> QA output created by 486
> No data available
> error=22 at line 63

This is a regression test for a kernel patch; the XATTR_REPLACE is
supposed to succeed if you've added the fix.  If it throws any kind of
error then the kernel is misbehaving, but it doesn't really matter which
error we get.

However, we could just get rid of the redundant error=%d printing,
seeing as we just perror'd anyway.

--D

> ----------------------------------------------------------------
> 
> We want to save the correct errno and print it after calling perror().
> 
> It seems that only calling perror() didn't change the errno, but calling
> perror() and redirecting the output of perror() to a file set errno to
> EINVAL.
> 
> For example, running the special test.c to reproduce the issue:
> ------------------------------------------------------------
> #include <errno.h>
> #include <unistd.h>
> #include <stdio.h>
> 
> int main(void)
> {
>         close(-1);
>         printf("errno %d before\n", errno);
>         perror("");
>         printf("errno %d after\n", errno);
> }
> ------------------------------------------------------------
> # gcc -o test test.c
> # ./test
> # ./test 2>log
> 
> fdopen() called by perror() in glibc seems to set errno to EINVAL
> in some cases(e.g. the access mode of stderr is O_WRONLY). I am not
> sure whether this is a perror bug in glibc or not.
> 
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
> ---
>  src/attr_replace_test.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/src/attr_replace_test.c b/src/attr_replace_test.c
> index 23adc07..e9a08cc 100644
> --- a/src/attr_replace_test.c
> +++ b/src/attr_replace_test.c
> @@ -10,8 +10,9 @@
>  #include <sys/xattr.h>
>  #include <sys/stat.h>
>  
> -#define die() do { perror(""); \
> -fprintf(stderr, "error=%d at line %d\n", errno, __LINE__); \
> +#define die() do { int real_errno = errno; \
> +perror(""); \
> +fprintf(stderr, "error=%d at line %d\n", real_errno, __LINE__); \
>  exit(1); } while (0)
>  
>  #define fail(...) do { \
> -- 
> 1.8.3.1
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-05-16 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  8:00 [PATCH] generic/486: print correct errno Xiao Yang
2018-05-16 15:27 ` Darrick J. Wong [this message]
2018-05-17  1:36   ` [PATCH] generic/486: Get rid of the redundant error=%d printing Xiao Yang
2018-05-17  3:16     ` Eryu Guan
2018-05-17  3:25       ` Xiao Yang
2018-05-17  3:32       ` [PATCH v3] " Xiao Yang
2018-05-17 14:55         ` Darrick J. Wong

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=20180516152714.GA4910@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=libc-alpha-help@sourceware.org \
    --cc=yangx.jy@cn.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.