RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2046021 - kernel 4.18.0-358.el8 async dirops causes write errors with namespace restricted caps
Summary: kernel 4.18.0-358.el8 async dirops causes write errors with namespace restric...
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kernel
Version: CentOS Stream
Hardware: All
OS: All
Target Milestone: rc
: ---
Assignee: Jeff Layton
QA Contact: Yogesh Mane
John Wilkins
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-26 08:06 UTC by Dan van der Ster
Modified: 2022-05-10 16:14 UTC (History)
11 users (show)

Fixed In Version: kernel-4.18.0-372.1.1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-05-10 15:11:40 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 54013 0 None None None 2022-01-26 08:06:29 UTC
Gitlab redhat/rhel/src/kernel rhel-8 merge_requests 2065 0 None None None 2022-02-04 18:11:58 UTC
Red Hat Issue Tracker RHELPLAN-109738 0 None None None 2022-01-26 08:27:52 UTC
Red Hat Product Errata RHSA-2022:1988 0 None None None 2022-05-10 15:11:51 UTC

Description Dan van der Ster 2022-01-26 08:06:30 UTC
Description of problem:

kernel 4.18.0-358.el8 breaks the ceph client for clients with osd caps restricted to an osd namespace. This kernel was the first to enable async dirops by default; the issue was fixed by mounting with async dirops disabled (-owsync).
Details are in https://tracker.ceph.com/issues/54013

Version-Release number of selected component (if applicable):

kernel 4.18.0-358.el8

Also reproduced with upstream kernel 5.16.2

How to reproduce:

Mount a ceph file share with caps like

        key = xx==
        caps mds = "allow rw path=/volumes/_nogroup/xxx" 
        caps mon = "allow r" 
        caps osd = "allow rw pool=cephfs_data namespace=fsvolumens_xxx" 

Then try to untar a kernel, you'll get errors like

# tar xf linux-5.17-rc1.tar.gz 2>&1 | head
tar: linux-5.17-rc1/.get_maintainer.ignore: Cannot write: Operation not permitted
tar: linux-5.17-rc1/.gitattributes: Cannot write: Operation not permitted
tar: linux-5.17-rc1/.gitignore: Cannot write: Operation not permitted


This patch is the proposed fix: https://lore.kernel.org/ceph-devel/20220125211022.114286-1-jlayton@kernel.org/T/#u

Comment 28 errata-xmlrpc 2022-05-10 15:11:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: kernel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.