| Anonymous | Login | Signup for a new account | 11-10-2008 11:19 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001496 | [BusyBox] Other | major | always | 09-10-07 06:04 | 02-11-08 08:49 | ||||
| Reporter | whitpa | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | svn | ||||||
| Summary | 0001496: tftp applet never reaches timeout retry limit | ||||||||
| Description |
The "timeout" variable never gets a chance to get any smaller than TFTP_NUM_RETRIES-1, because it gets reset to TFTP_NUM_RETRIES on every loop iteration. I'm guessing that networking/tftp.c:221, which reads: timeout = TFTP_NUM_RETRIES; /* re-initialize */ ... ought to be somewhere *above* the "send_again" label! Not sure when this broke, exactly, but it's at least Busybox 1.6.0 onwards. |
||||||||
| Additional Information |
I consider this to be a major severity bug, because the tftp applet doesn't ever return control to my rc.sysinit script, ergo my system locks up and never enters any runlevel. |
||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |