Bug 131788 - should not need write access to .ko files
should not need write access to .ko files
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: module-init-tools (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks: FC3SELinux FC4Target
  Show dependency treegraph
 
Reported: 2004-09-04 11:32 EDT by Russell Coker
Modified: 2014-03-16 22:47 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-01-25 14:37:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Russell Coker 2004-09-04 11:32:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
To lock the module insmod will open the file read/write.  I think that it should not open it for write.

Won't a read-lock do everything that's needed?

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


How reproducible:
Always

Steps to Reproduce:
.

Additional info:
Comment 1 Bill Nottingham 2004-10-12 23:47:34 EDT
The locking isn't to prevent overwriting of the module, it's to
prevent multiple concurrent attempted installs of the same module. So,
any sort of read lock wouldn't work here.
Comment 2 Bill Nottingham 2005-01-25 14:37:07 EST
Considering the purpose of the lock, closing. I suppose any changes
with it need taken upstream.

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