Bug 160528

Summary: audit: file system watch on block device
Product: Red Hat Enterprise Linux 4 Reporter: Steve Grubb <sgrubb>
Component: kernelAssignee: David Woodhouse <dwmw2>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: high    
Version: 4.0CC: khake, krisw
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2005-514 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-05 13:30:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 113381, 156322    

Description Steve Grubb 2005-06-15 16:02:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
When file system watches are set on block devices and triggered, it overflows the backlog many, many times. Block devices do not need to be watched and something may be done to disallow monitoring them. This also points out a case where some rate limiting on syscall exit may be done.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. New feature

Additional info:

Comment 1 David Woodhouse 2005-06-20 13:38:34 UTC
There's a more generic problem here with the backlog overflowing.

We can slow down the process being audited by making it wait for space on the
backlog queue instead of just failing. This is done in audit.63.

Comment 4 Red Hat Bugzilla 2005-10-05 13:30:43 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 the 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/RHSA-2005-514.html