From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 197069] systemd service with ProtectHome=yes causes ELOOP when accessing /home
Date: Sun, 01 Oct 2017 00:37:13 +0000 [thread overview]
Message-ID: <bug-197069-13602-xqvKTGSFVW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197069-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197069
Theodore Tso (tytso@mit.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |INVALID
--- Comment #6 from Theodore Tso (tytso@mit.edu) ---
The Fedora bug report you referenced indicates that it is fixed by installing
systemd 232 or above.
I suggest you post a bugfix in bug tracker system used by your distribution.
And if their answer is they don't support newer kernels on an older / obsolete
distribution, then that's your answer.
You indicated you are using Red Hat 7.0. I'm going to assume that's RHEL 7.0,
which is based on a 3.10 kernel, and a systemd from 3+ years ago. If things
fall apart when you try installing a newer kernel, that won't be the first time
RHEL has compatibility problems with newer kernels. If you are using RHEL 7,
that generally means you value stability more than you do new features. If you
want to be using a newer kernel, you should try upgrading to a more modern
distribution *first*.
If you are indeed using RHEL, then the place to ask is the Red Hat Support. I
can tell you that using a 4.4 or 4.9 kernel is not a supported kernel, so it
may very well be that the answer is that there is no right place, and what you
are doing is just not anything anyone is interested in supporting. If you want
to pay someone enough money, or you want to retain your own Linux experts, I'm
sure they might be able to make it work --- as the old NASA saying goes,
"anything will fly if you give it enough thrust" --- but it's highly likely no
one is going to be interested in supporting you for free.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2017-10-01 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 20:17 [Bug 197069] New: systemd service with ProtectHome=yes causes ELOOP when accessing /home bugzilla-daemon
2017-09-30 0:34 ` [Bug 197069] " 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 [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=bug-197069-13602-xqvKTGSFVW@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).