This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 443808 - NFSv4 regression after 2.6.5 (nfsv4 write status NFS4ERR_ACCES but kernel ::write status EIO)
NFSv4 regression after 2.6.5 (nfsv4 write status NFS4ERR_ACCES but kernel ::...
Product: Fedora
Classification: Fedora
Component: nfs-utils (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Steve Dickson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-23 10:02 EDT by Meflah Abdelkader
Modified: 2009-01-09 02:47 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 02:47:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Meflah Abdelkader 2008-04-23 10:02:45 EDT
Description of problem:
The kernel return EIO instead of EACCES error (the nfsv4 server returns 

Version-Release number of selected component (if applicable):
from 2.6.21 to 2.6.25

How reproducible:
mount -o noac -t nfs4 ... 
NFSv4 client 1:
  - open existing file (locktest) for read/write
  - set a shared lock range:0x4000-0x9fff via fcntl(fd, F_SETLKW, &flock)
  - wait client 2
NFSv4 client 2:
  - open existing file (locktest) for read/write
  - write ranges 0x0000-0x1fff
  - write ranges 0x0000-0x3fff
  - write ranges 0x2000-0x5fff  EIO instead of EACCES

Steps to Reproduce:
1. mount -o noac -t nfs4 ...
2. client1 open file and takes a lock on interval 0x4000-0x9fff 
3. client2 open file and does writes before, in and after intervals 0x4000-
Actual results:
status of write in locked interval is EIO 

Expected results:

Additional info:
Comment 1 Bug Zapper 2008-11-26 05:33:05 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here:
Comment 2 Bug Zapper 2009-01-09 02:47:26 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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