Bug 484835 - fuser -m <dev> doesn't work after lazy unmount
fuser -m <dev> doesn't work after lazy unmount
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: psmisc (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Daniel Novotny
: Regression
Depends On:
Blocks: 494834 497303
  Show dependency treegraph
Reported: 2009-02-10 03:20 EST by Tomas Smetana
Modified: 2013-04-12 16:04 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 497303 (view as bug list)
Last Closed: 2009-04-22 08:44:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
the patch from the upstream applies cleanly and I tested it works on rhel5 (3.98 KB, patch)
2009-02-10 06:21 EST, Daniel Novotny
no flags Details | Diff

  None (edit)
Description Tomas Smetana 2009-02-10 03:20:58 EST
Description of problem:
fuser -m <device> fails to detect open files on a filesystem that has been lazily unmounted.
This is bad since a typical use case for "fuser -m" is to kill remaining users of a filesystem.

How reproducible:

Steps to Reproduce:
dd if=/dev/zero of=fs.img bs=1M count=100
losetup /dev/loop4 fs.img
mkfs.ext2 /dev/loop4
mkdir mnt
mount /dev/loop4 mnt
touch mnt/testfile
less mnt/testfile
# these will work and display PID of less
fuser -m mnt
fuser -m /dev/loop4
# lazy umount!! as there's open file it's actually still mounted and
already open files can be accessed
umount -l mnt
fuser -m /dev/loop4
# doesn't find anything!!

Actual results:
two first fuser runs report the pid last does not

Expected results:
fuser reports the pid in all cases

Additional info:
Bug has been already reported to upstream including a patch:
Comment 2 RHEL Product and Program Management 2009-02-10 03:42:20 EST
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.
Comment 3 Daniel Novotny 2009-02-10 06:21:22 EST
Created attachment 331413 [details]
the patch from the upstream applies cleanly and I tested it works on rhel5
Comment 4 J.H.M. Dassen (Ray) 2009-02-10 06:51:53 EST
Daniel, could you (or Tomas) add a note to that affect to the upstream defect
report then please? 

The upstream report was filed by the customer directly; having a public ack
from your side is likely to increase the chances of it quickly being
reviewed/accepted upstream.
Comment 5 Daniel Novotny 2009-02-10 07:08:48 EST
OK, added a note to the upstream bug tracker
Comment 8 Daniel Novotny 2009-04-14 09:28:36 EDT
fixed in psmisc-22.2-7
Comment 12 errata-xmlrpc 2009-04-22 08:44:22 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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