From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jiri Kosina <jkosina@suse.cz>, Michal Schmidt <mschmidt@redhat.com>
Subject: [PULL] module and param
Date: Tue, 25 Oct 2011 14:13:59 +1030 [thread overview]
Message-ID: <87mxcppwg0.fsf@rustcorp.com.au> (raw)
(Via github, returning to kernel.org is on my TODO list...)
The following changes since commit 1bf1aacedcda23c75e70fa3394e1caa6d4b5ee49:
Merge branch 'samsung-fixes-4' of git://github.com/kgene/linux-samsung (2011-10-23 10:44:40 +0300)
are available in the git repository at:
git://github.com/rustyrussell/linux.git master
Jiri Kosina (1):
kmod: prevent kmod_loop_msg overflow in __request_module()
Michal Schmidt (1):
params: make dashes and underscores in parameter names truly equal
include/linux/moduleparam.h | 20 ++++++++++++++++++++
init/main.c | 4 ++--
kernel/kmod.c | 4 +++-
kernel/params.c | 21 ++++++++++++++-------
4 files changed, 39 insertions(+), 10 deletions(-)
commit ea1c71de56fb2799da9d6f26778c7ddf5f42c4a3
Author: Jiri Kosina <jkosina@suse.cz>
Date: Tue Oct 25 11:53:31 2011 +1030
kmod: prevent kmod_loop_msg overflow in __request_module()
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>
CC: stable@kernel.org
kernel/kmod.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
commit 14377d658e711ef2301db023370aeaa48a466401
Author: Michal Schmidt <mschmidt@redhat.com>
Date: Mon Oct 10 00:03:37 2011 +0200
params: make dashes and underscores in parameter names truly equal
The user may use "foo-bar" for a kernel parameter defined as "foo_bar".
Make sure it works the other way around too.
Apply the equality of dashes and underscores on early_params and __setup
params as well.
The example given in Documentation/kernel-parameters.txt indicates that
this is the intended behaviour.
With the patch the kernel accepts "log-buf-len=1M" as expected.
https://bugzilla.redhat.com/show_bug.cgi?id=744545
Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (neatened implementations)
include/linux/moduleparam.h | 20 ++++++++++++++++++++
init/main.c | 4 ++--
kernel/params.c | 21 ++++++++++++++-------
3 files changed, 36 insertions(+), 9 deletions(-)
next reply other threads:[~2011-10-25 3:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 3:43 Rusty Russell [this message]
2011-10-25 7:33 ` [PULL] module and param Linus Torvalds
2011-10-26 2:43 ` Rusty Russell
2011-10-26 12:45 ` Linus Torvalds
2011-10-27 0:45 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2012-03-26 2:34 Rusty Russell
2012-01-12 23:13 Rusty Russell
2011-01-24 4:07 Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mxcppwg0.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).