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.

Description of problem:
Copied from the description of the test case:
inline symlinks are removed from the inode when an extended attributes forces it into being remote symlink. Warning: this test will ASSERT on unpatched DEBUG XFS.

Version-Release number of selected component (if applicable):
kernel-3.10.0-23.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run the xfstests test case xfs/298 for xfs fs
2. Check the output

Actual results:
For symlink size 128, the core.nextents is reported to be 1.

Expected results:
The core.nextents is 0.

Additional info:
This seems to have been fixed upstream by [v4] xfs: fix the symbolic link assert in xfs_ifree:
http://patchwork.xfs.org/patch/5614/

Ok, this should be fixed in:

commit 725eb1eb2ae88c200466fec34bcf1fbce4b8eca3
Author: Mark Tinguely <tinguely>
Date:   Mon Jun 17 15:35:57 2013 -0500

    xfs: fix the symbolic link assert in xfs_ifree
    
    Adding an extended attribute to a symbolic link can force that
    link to an remote extent. xfs_inactive() incorrectly assumes
    that any symbolic link small enough to be in the inode core
    is incore, resulting in the remote extent to not be removed.
    xfs_ifree() will assert on presence of this leaked remote extent.
    
    Signed-off-by: Mark Tinguely <tinguely>
    Reviewed-by: Ben Myers <bpm>
    Signed-off-by: Ben Myers <bpm>

which hit:

v3.11-rc1

and should eventually be in RHEL7... when bug #1001861 is done, please retest, and dup this one I guess, if it passes?

Assigning to Dave, but this will probably end up just being a dup.

Thanks,
-Eric

kernel-3.10.0-89.el7 passed xfs/298, closed as CURRENTRELEASE.