Re: [patch 2/2] track and print last unloaded module in the oops trace
- From: DM <dm.n9107@xxxxxxxxx>
- Date: Tue, 8 Jan 2008 14:51:37 +0100
On Jan 7, 2008 12:19 AM, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
[...]
This patch tracks the last unloaded module, and prints this as part of the[...]
module list in the oops trace.
}
+ /* Store the name of the last unloaded module for diagnostic purposes */
+ sprintf(last_unloaded_module, mod->name);
free_module(mod);
Why use sprintf? If a module name contains the % character we could
overflow the buffer. Or is module-unloading root-only and we don't
care?
Best regards,
dm.n9107
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [patch 2/2] track and print last unloaded module in the oops trace
- From: Arjan van de Ven
- Re: [patch 2/2] track and print last unloaded module in the oops trace
- References:
- [patch 2/2] track and print last unloaded module in the oops trace
- From: Arjan van de Ven
- [patch 2/2] track and print last unloaded module in the oops trace
- Prev by Date: Re: [PATCH][RFC] Simple tamper-proof device filesystem.
- Next by Date: Re: [GIT PATCH] SCSI bug fixes for 2.6.24-rc3
- Previous by thread: Re: [patch 2/2] track and print last unloaded module in the oops trace
- Next by thread: Re: [patch 2/2] track and print last unloaded module in the oops trace
- Index(es):
Relevant Pages
|
Loading