public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "william.wilson at canonical dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28377] New: closefrom_fallback fails when /proc/self/fd is not present, which causes unexpected behavior with openssh
Date: Wed, 22 Sep 2021 22:35:58 +0000	[thread overview]
Message-ID: <bug-28377-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=28377

            Bug ID: 28377
           Summary: closefrom_fallback fails when /proc/self/fd is not
                    present, which causes unexpected behavior with openssh
           Product: glibc
           Version: 2.34
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: william.wilson at canonical dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

A valid use case of sshd is to run in a "chroot" that actually looks nothing
like a root filesystem. If this is attempted in a kernel that does not
implement the close_range syscall (5.8 or older) the fallback_closefrom
function in glibc 2.34 looks for /proc/self/fd and returns an error if it is
not found. This implementation may want to consider scenarios where
/proc/self/fd is not present.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-09-22 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 22:35 william.wilson at canonical dot com [this message]
2021-09-22 22:37 ` [Bug libc/28377] " william.wilson at canonical dot com
2021-09-22 23:07 ` michael.hudson at canonical dot com
2021-09-27 13:18 ` adhemerval.zanella at linaro dot org

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=bug-28377-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).