Bug 1359042 - /etc/exports parsing is broken leading default option cannot be overridden by the host-specific option
Summary: /etc/exports parsing is broken leading default option cannot be overridden by...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
Milan Navratil
Depends On:
Blocks: 1362179
TreeView+ depends on / blocked
Reported: 2016-07-22 07:17 UTC by Yongcheng Yang
Modified: 2020-12-15 07:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
The default option specification is not overridden by the host-specific option in `/etc/exports` When "sec=sys" is used in the default option section of the `/etc/exports` file, the options list that follows is not parsed correctly. As a consequence, the default option cannot be overridden by the host-specific option.
Clone Of:
Last Closed: 2020-12-15 07:43:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Yongcheng Yang 2016-07-22 07:17:31 UTC
Description of problem:
The default option specification (i.e. ‘ro’) should be overridden by the host-specific option. That’s how it used to work.

Version-Release number of selected component (if applicable):
RHEL-7.2 with nfs-utils-1.3.0-0.31.el7

How reproducible:
100% easy

Steps to Reproduce:
1. See "Actual results" below.

Actual results:
[root@leira nfs]# cat /etc/exports
/export         -ro,sec=sys,sync        localhost(rw,no_root_squash)
[root@leira nfs]# exportfs -rv
exporting localhost:/export
[root@leira nfs]# mount -t nfs localhost:/export /mnt/nfs
[root@leira nfs]# mkdir /mnt/nfs/gnurr
mkdir: cannot create directory ‘/mnt/nfs/gnurr’: Read-only file system

Note that removing the "sec=sys" above causes the test to succeed.

Expected results:
localhost should have the "rw" right.

Additional info:
upstream conversation

Comment 11 RHEL Program Management 2020-12-15 07:43:11 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

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