#4184 BLOC First D: JFFS2 Dirent Anomaly

[Zarro Boogs per Child]

#4184: JFFS2 Dirent Anomaly
--------------------------------+-------------------------------------------
  Reporter:  wmb at firmworks.com  |       Owner:  mstone                
      Type:  defect             |      Status:  new                   
  Priority:  blocker            |   Milestone:  First Deployment, V1.0
 Component:  kernel             |     Version:                        
Resolution:                     |    Keywords:                        
  Verified:  0                  |  
--------------------------------+-------------------------------------------

Comment(by wmb at firmworks.com):

 Regarding (c) above, i.e. "c) For some unknown reason, reading those
 modules causes "copy-on-write link breakage", ..."

 Well, it turns out that modprobe opens .ko files in Read/Write mode.

 Why does it do that?  So it can support the --force* options, in which it
 attempts to remove version information from the module file to override
 mismatches with the kernel version. It opens R/W regardless of whether any
 --force* option is present.

 IMHO, that is a bad idea.  Munging a module file should be done with a
 separate command.

 insmod does not do that bad thing - it opens the module file read-only.

-- 
Ticket URL: <https://dev.laptop.org/ticket/4184#comment:13>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system