From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 197069] New: systemd service with ProtectHome=yes causes ELOOP when accessing /home
Date: Thu, 28 Sep 2017 20:17:05 +0000 [thread overview]
Message-ID: <bug-197069-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=197069
Bug ID: 197069
Summary: systemd service with ProtectHome=yes causes ELOOP when
accessing /home
Product: File System
Version: 2.5
Kernel Version: kernel-lt 4.4 and 4.9 series
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: xxjack12xx@gmail.com
Regression: No
Description of problem:
Having ProtectHome=yes in any service file causes a symlinked or autofs mounted
/home directory to return ELOOP
ls: cannot open directory /home: Too many levels of symbolic links
Version-Release number of selected component (if applicable):
Red Hat 7.0+
How reproducible:
1. Start a service with ProtectHome=yes
2. Start autofs with /home automounted
3. Access to /home returns ELOOP
ls: cannot open directory /home: Too many levels of symbolic links
Additional info:
This Fedora bug report describes the issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1444223
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2017-09-28 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 20:17 bugzilla-daemon [this message]
2017-09-30 0:34 ` [Bug 197069] systemd service with ProtectHome=yes causes ELOOP when accessing /home bugzilla-daemon
2017-09-30 1:04 ` bugzilla-daemon
2017-09-30 1:07 ` bugzilla-daemon
2017-09-30 5:28 ` bugzilla-daemon
2017-09-30 7:40 ` bugzilla-daemon
2017-10-01 0:37 ` bugzilla-daemon
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-197069-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).