|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ View Advanced ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0001027 |
[buildroot] Other |
minor |
always |
09-12-06 06:43 |
02-12-07 05:34 |
|
|
Reporter |
raburton |
View Status |
public |
|
|
Assigned To |
buildroot |
|
Priority |
normal |
Resolution |
open |
|
|
Status |
assigned |
|
Product Version |
0.9.27 |
|
|
Summary |
0001027: problem in cramfs endianness patch when padding enabled |
|
Description |
The endianness patch for cramfs should allow the cramfsck command to process images of either endianness transparently. However it cannot handle images of the opposite endianness to the host that have padding enabled (built with the -p option).
I have attached a replacement cramfs-02-endian.patch (rather than a patch against the patch) that fixes this issue, but is otherwise identical to the original. |
|
Additional Information |
Problem was caused by assuming that, in the case of a padded image, the need for swapping had alreay been determined. However if padding has been enabled we have not yet found the eyecatcher, in fact the affected code is still looking for it, and so we have not determined if swapping is needed. We are in an else block that can only be reached if the eyecatcher, and so swapping state, has not yet been found. |
|
|
Attached Files |
 new-cramfs-02-endian.patch [^] (8,424 bytes) 09-12-06 06:43 |
|
|
Relationships 
