public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, libc-alpha@sourceware.org
Subject: Re: [PATCH 0/5] Linux: lchmod and AT_SYMLINK_NOFOLLOW support for fchmodat
Date: Mon, 17 Aug 2020 18:46:34 +0300	[thread overview]
Message-ID: <20200817154634.GA32014@altlinux.org> (raw)
In-Reply-To: <87blk9ry5d.fsf@oldenburg2.str.redhat.com>

On Tue, Jul 21, 2020 at 11:54:38AM +0200, Florian Weimer via Libc-alpha wrote:
> * Andreas Schwab:
> > On Jan 22 2020, Florian Weimer wrote:
> >
> >> These patches use the O_PATH hack to implement a fairly close
> >> approximation of fchmodat in AT_SYMLINK_NOFOLLOW mode.
> >
> > This means that cp -a now fails when /proc is not mounted.
> >
> > <https://build.opensuse.org/package/live_build_log/home:Andreas_Schwab:glibc:rebuild/installation-images:openSUSE/f/x86_64>
> >
> > running "cp -a /var/lib/ca-certificates var/lib"
> > cp: setting permissions for 'var/lib/ca-certificates/pem': Operation not supported
> > cp: setting permissions for 'var/lib/ca-certificates/openssl': Operation not supported
> >
> > newfstatat(AT_FDCWD, "/var/lib/ca-certificates/pem", {st_mode=S_IFDIR|0500, st_size=4096, ...}, AT_SYMLINK_NOFOLLOW) = 0
> > mkdir("var/lib/ca-certificates/pem", 0500) = 0
> > lstat("var/lib/ca-certificates/pem", {st_mode=S_IFDIR|0500, st_size=4096, ...}) = 0
> > openat(AT_FDCWD, "var/lib/ca-certificates/pem", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) = 3
> > newfstatat(3, "", {st_mode=S_IFDIR|0500, st_size=4096, ...}, AT_EMPTY_PATH) = 0
> > chmod("/proc/self/fd/3", 040700)        = -1 ENOENT (No such file or directory)
> > close(3)                                = 0
> > write(2, "cp: ", 4)                     = 4
> > write(2, "setting permissions for 'var/lib"..., 53) = 53
> > write(2, ": Operation not supported", 25) = 25
> > write(2, "\n", 1)                       = 1
> 
> Yes, it's a known issue.

Sorry but this is a regression, we cannot assume that /proc is always mounted.


-- 
ldv

  reply	other threads:[~2020-08-17 15:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 20:03 Florian Weimer
2020-01-22 20:03 ` [PATCH 1/5] support: Add the xlstat function Florian Weimer
2020-01-22 20:03 ` [PATCH 3/5] Linux: Emulate fchmodat with AT_SYMLINK_NOFOLLOW using O_PATH [BZ #14578] Florian Weimer
2020-02-09  8:31   ` Paul Eggert
2020-02-09  8:58     ` Florian Weimer
2020-02-09 10:06       ` Paul Eggert
2020-02-09 10:33         ` Florian Weimer
2020-02-11 15:25         ` Florian Weimer
2020-02-12  1:37           ` Paul Eggert
2020-01-22 20:03 ` [PATCH 2/5] io: Implement lchmod using fchmodat " Florian Weimer
2020-01-22 20:04 ` [PATCH 4/5] io: Add io/tst-lchmod covering lchmod and fchmodat Florian Weimer
2020-02-11 15:27   ` Florian Weimer
2020-02-12 18:52     ` Adhemerval Zanella
2020-02-12 18:55       ` Florian Weimer
2020-02-12 19:41         ` Adhemerval Zanella
2020-02-12 20:01           ` Florian Weimer
2020-02-12 20:28             ` Florian Weimer
2020-01-22 20:27 ` [PATCH 5/5] Linux: Add op/tst-o_path-locks Florian Weimer
2020-07-21  9:46 ` [PATCH 0/5] Linux: lchmod and AT_SYMLINK_NOFOLLOW support for fchmodat Andreas Schwab
2020-07-21  9:54   ` Florian Weimer
2020-08-17 15:46     ` Dmitry V. Levin [this message]
2020-08-25 10:21     ` Andreas Schwab
2020-08-25 10:24       ` Florian Weimer
2020-08-25 10:53         ` Andreas Schwab
2020-08-25 11:04           ` Florian Weimer
2020-08-25 11:08             ` Andreas Schwab
2020-08-25 11:09               ` Florian Weimer
2020-08-25 11:15                 ` Andreas Schwab
2020-08-25 11:16                   ` Florian Weimer
2020-08-25 11:22                     ` Andreas Schwab
2020-08-25 11:28                       ` Florian Weimer
2020-08-25 12:13                         ` Andreas Schwab
2020-08-25 12:16                           ` Florian Weimer

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=20200817154634.GA32014@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@linux-m68k.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 read-only IMAP folder(s) and NNTP newsgroup(s).