Anonymous | Login | Signup for a new account | 11-10-2008 10:50 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 | ||||
0000468 | [BusyBox] Kernel Module Support | minor | always | 10-04-05 12:37 | 12-14-05 19:54 | ||||
Reporter | mbizon | View Status | public | ||||||
Assigned To | BusyBox | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 1.01 | ||||||
Summary | 0000468: rmmod does not report failure | ||||||||
Description |
rmmod does not return failure when module unload fails (at least it does not on my system). The syscall() returned a non zero value but a positive one, while rmmod checks only for negative values. As the insmod code use syscall() in quite the same way and checks for non zero, I guess it is a mistake. Attached trivial patch to fix this. |
||||||||
Additional Information | |||||||||
Attached Files | rmmod_syscall_ret.patch [^] (652 bytes) 10-04-05 12:37 | ||||||||
|
Copyright © 2000 - 2006 Mantis Group |