#4184 BLOC First D: JFFS2 Dirent Anomaly

[Zarro Boogs per Child]

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

Comment(by wmb at firmworks.com):

 I don't think the loop hypothesis is necessary.  dwmw has already figured
 out how the infinite copying happens, as a result of an issue with the way
 garbage collection was working.

 The question we have now is "how did a name with a null included as part
 of the length get created in the  first place".

 I have my own speculation to add to the mix: Look for some place in some
 code where the file name is represented as address, length instead of
 C-style "address of string implicitly assumed to be null-terminated".
 Only with the addr,len representation could a trailing null possibly
 survive.  Then work upwards until you find where the addr,len
 representation is generated.  I suspect something like an inappropriate
 "length = strlen(s)+1".

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