| commit | 3cdf240310b4f3d94981d727d3660c78a50a40c6 | |
| author | Jiri Kosina <jkosina@suse.cz> | |
| Wed, 26 Oct 2011 02:40:39 +0000 (26 13:10 +1030) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 11 Nov 2011 17:35:48 +0000 (11 09:35 -0800) | ||
| tree | fae7019c027ef93773110db514fa39f63cff46f5 | treesnapshot (tar.gz zip) |
| parent | 50f621d8f5b6f9e8ed931df12c595fd0e882f8e3 | commitdiff |
kmod: prevent kmod_loop_msg overflow in __request_module()
commit 37252db6aa576c34fd794a5a54fb32d7a8b3a07a upstream.
Due to post-increment in condition of kmod_loop_msg in __request_module(),
the system log can be spammed by much more than 5 instances of the 'runaway
loop' message if the number of events triggering it makes the kmod_loop_msg
to overflow.
Fix that by making sure we never increment it past the threshold.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 37252db6aa576c34fd794a5a54fb32d7a8b3a07a upstream.
Due to post-increment in condition of kmod_loop_msg in __request_module(),
the system log can be spammed by much more than 5 instances of the 'runaway
loop' message if the number of events triggering it makes the kmod_loop_msg
to overflow.
Fix that by making sure we never increment it past the threshold.
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| kernel/kmod.c | diffblobblamehistory |