From: Stephen Hemminger <stephen@networkplumber.org>
To: Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org
Subject: Fw: [Bug 220921] New: nfs bug , mountig nfs volume
Date: Mon, 29 Dec 2025 15:08:31 -0800 [thread overview]
Message-ID: <20251229150831.2c6af85f@phoenix.local> (raw)
Begin forwarded message:
Date: Mon, 29 Dec 2025 23:01:41 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 220921] New: nfs bug , mountig nfs volume
https://bugzilla.kernel.org/show_bug.cgi?id=220921
Bug ID: 220921
Summary: nfs bug , mountig nfs volume
Product: Networking
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Other
Assignee: stephen@networkplumber.org
Reporter: walter.moeller@moeller-it.net
Regression: No
# 1. Bug-Report an LKML/kernel.org:
# Titel: "NFS: EPERM on dangling symlinks to unmounted NFS volumes breaks
userspace (Portage)"
# Details:
# - Kernel 6.19-rc3 vanilla-sources
# - Symlink zu nicht-gemounteten NFS-Volume
# - emerge/Portage schlägt fehl mit "Operation not permitted"
# - Regression von 6.18.2
# 2. Temporärer Workaround:
# - Link umbenennen (hast du gemacht ✓)
# - Oder NFS-Volume mounten
# - Oder bei 6.18.2 bleiben
Kernel-Regression bestätigt:
6.18.2: Ignoriert Links auf nicht-gemountete NFS-Volumes
6.19-rc3: Wirft "Operation not permitted" und bricht ab
Das ist ein Kernel-Bug der gefixt werden muss!
Regards walter möller
ps: uahc kernel 6.18-rc3 !!!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2025-12-29 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 23:08 Stephen Hemminger [this message]
2025-12-30 14:12 ` Fw: [Bug 220921] New: nfs bug , mountig nfs volume Chuck Lever
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=20251229150831.2c6af85f@phoenix.local \
--to=stephen@networkplumber.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/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).