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.

+++ This bug was initially created as a clone of Bug #1014308 +++

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/

This is also reproducible in RHEL 6 (kernel-2.6.32-419.el6).

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

*** Bug 1088730 has been marked as a duplicate of this bug. ***

725eb1e xfs: fix the symbolic link assert in xfs_ifree

hm, possibly depending on

commit b373e98daa70d7ddb10f53f81e711c4d17651795
Author: Christoph Hellwig <hch>
Date:   Wed Jul 4 11:13:29 2012 -0400

    xfs: clean up xfs_inactive

Will have to decide how important this one really is.

I'm going to close this as WONTFIX for now; it's not a trivial upstream patch application and the bug, as far as we know, is only seen in the xfstest specifically designed to trigger it.

If we get a customer report of the problem, we can re-open & re-examine this bug.