util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: Re: [PATCH] ipcs,chmem: fix access() usage
Date: Mon, 25 Jun 2018 16:52:21 +0200	[thread overview]
Message-ID: <201806251652.21950.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20180625121831.14610-1-sweet_f_a@gmx.de>

I've submitted this and 2 more trivial fixes via github
https://github.com/karelzak/util-linux/pull/653

On Monday 25 June 2018, Ruediger Meier wrote:
> From: Ruediger Meier <ruediger.meier@ga-group.nl>
>
> Some mistakes happened lately when switching from path_exist()
> to ul_path_access(). See f09a98de and 8ca31279.
>
> This caused ipcs tests failures when running i386 binaries on x86_64
> hosts, because the syscall fallback was always used. That's why I
> reviewed all similar changes and found another one in chmem.
>

      reply	other threads:[~2018-06-25 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 12:18 [PATCH] ipcs,chmem: fix access() usage Ruediger Meier
2018-06-25 14:52 ` Ruediger Meier [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=201806251652.21950.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).