Bug 484835 - fuser -m <dev> doesn't work after lazy unmount
Summary: fuser -m <dev> doesn't work after lazy unmount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: psmisc
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Novotny
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks: 494834 497303
TreeView+ depends on / blocked
 
Reported: 2009-02-10 08:20 UTC by Tomas Smetana
Modified: 2018-10-20 01:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 497303 (view as bug list)
Environment:
Last Closed: 2009-04-22 12:44:22 UTC
Target Upstream Version:
Embargoed:


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 11:21 UTC, Daniel Novotny
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0439 0 normal SHIPPED_LIVE psmisc bug fix update 2009-04-22 12:44:19 UTC

Description Tomas Smetana 2009-02-10 08:20:58 UTC
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:
always

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
<CTRL>-Z
# 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:
https://sourceforge.net/tracker/index.php?func=detail&aid=2545632&group_id=15273&atid=115273

Comment 2 RHEL Program Management 2009-02-10 08:42:20 UTC
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 11:21:22 UTC
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 11:51:53 UTC
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 12:08:48 UTC
OK, added a note to the upstream bug tracker

Comment 8 Daniel Novotny 2009-04-14 13:28:36 UTC
fixed in psmisc-22.2-7

Comment 12 errata-xmlrpc 2009-04-22 12:44:22 UTC
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.

http://rhn.redhat.com/errata/RHBA-2009-0439.html


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