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: Sat, 30 Sep 2017 07:40:36 +0000 [thread overview]
Message-ID: <bug-197069-13602-qDhC6ppuHe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197069-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197069
Jack (xxjack12xx@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #5 from Jack (xxjack12xx@gmail.com) ---
Your opinion that I made a mistake in opening bug reports in random bug
trackers and trying to win friends in a place where I'm sure it wouldn't help
either way is very condescending. I'm reporting this bug because this bug
happens in the kernel series 4.4 and 4.9 lt series after the commit I had
mentioned previously. The bug does not happen in the same 4.4 and 4.9 series
before the commit.
Instead of closing my issue, how about helping me find the correct place to
report it? Obviously I don't know where I should file it under because I seem
to have posted it in a random place.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-09-30 7:40 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 [this message]
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-qDhC6ppuHe@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).