lkml.org 
[lkml]   [2011]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PULL] module and param
[ Cut-and-paste reply: mentally just "sed s/9p/module/g" ]

So for the merge window, I *really* want the development trees I pull
from explicitly verified some way.

Now, the p9 patches seem to be small enough, and not core enough, for
me to care deeply, but I really *really* want to not see unsigned
github things.

Putting a signed tag on there somewhere that actually signs the top
commit *and* mentions the repository and branch it is on (ie github)
is not wonderfully convenient, but it's at least relatively
straightforward (do I have a gpg key I can trust?).

Or using a host that I can trust is being maintained by you guys (or
some trusted third party like kernel.org).

(Also, I'm only seeing about half the patches mentioned in linux-next. Hmm?)

Please? Not pulled.

Linus

On Tue, Oct 25, 2011 at 5:43 AM, Rusty Russell <rusty@rustcorp.com.au> wrote:
> (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(-)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2011-10-25 09:35    [W:1.010 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site