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 1304626 - ltp ftruncate fails
Summary: ltp ftruncate fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel-aarch64
Version: 7.3
Hardware: aarch64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steve Whitehouse
QA Contact: Jeff Bastian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-04 08:47 UTC by Bill Peck
Modified: 2016-11-03 22:20 UTC (History)
4 users (show)

Fixed In Version: kernel-aarch64-4.5.0-0.rc5.29.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 22:20:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2145 0 normal SHIPPED_LIVE kernel-aarch64 bug fix and enhancement update 2016-11-03 13:11:35 UTC

Description Bill Peck 2016-02-04 08:47:35 UTC 
Description of problem:

ltp-lite ftruncate fails on aarch64.

ftruncate04                    FAIL       2    
ftruncate04_64                 FAIL       2    

Version-Release number of selected component (if applicable):
4.5.0-0.rc2.25.el7

How reproducible:
everytime

Steps to Reproduce:
1. execute ltp-lite task from beaker

Additional info:
will provide beaker links in followup comment
Comment 3 Mark Langsdorf 2016-02-17 18:48:54 UTC 
appears to be related to the mandatory locking option

the command line below fails
sudo mount -o loop,mand test.img /mnt

the command lines below succeeds
sudo mount -o loop,nomand test.img /mnt
sudo mount -o loop test.img /mnt
Comment 4 Jan Stancek 2016-02-19 15:15:06 UTC 
Presumably because of this commit:
  commit 9e8925b67a809bb27ce4b7d352d67f25cf1d7fc5
  Author: Jeff Layton <jeff.layton>
  Date:   Mon Nov 16 09:49:34 2015 -0500
    locks: Allow disabling mandatory locking at compile time

@@ -2677,6 +2685,8 @@ long do_mount(const char *dev_name, const char __user *dir_name,
                                   type_page, flags, data_page);
        if (!retval && !may_mount())
                retval = -EPERM;
+       if (!retval && (flags & MS_MANDLOCK) && !may_mandlock())
+               retval = -EPERM;


$ git tag --contains 9e8925b67a809bb27ce4b7d352d67f25cf1d7fc5
v4.5-rc1
v4.5-rc2
v4.5-rc3

This matches KT1 results, this test was working up to kernel-4.4.0-0.23.el7.

# grep MANDATORY /boot/config-4.5.0-0.rc4.28.el7.aarch64 
# CONFIG_MANDATORY_FILE_LOCKING is not set

Upstream defaults to 'y'.
Comment 8 errata-xmlrpc 2016-11-03 22:20:21 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, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHBA-2016-2145.html
Note You need to log in before you can comment on or make changes to this bug.