linux-kernel - Re: [PATCH 0/1] watchdog: parameters to control hard and soft lockup detector individually

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Oct 2014 10:56:12 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Ulrich Obergfell <uobergfe@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] watchdog: parameters to control hard and soft lockup
 detector individually

On Mon, Oct 13, 2014 at 04:32:41PM +0200, Ulrich Obergfell wrote:
> This post follows up to https://lkml.org/lkml/2014/8/11/329.
> During the discussion of that patch, Ingo Molnar commented in
> https://lkml.org/lkml/2014/8/18/577.
> 
>  "The softlockup and hardlockup detection control variables 
>   should be in separate flags, inside and outside the kernel - 
>   they (should) not relate to each other."
> 
> Please refer to [PATCH 1/1] for a description of the proposed
> changes of the 'user interface' in /proc/sys/kernel and kernel
> command line parameters.

Hi Uli,

Andrew just posted some of your other patches upstream for v3.18-rc1.
Let's try to rebase these changes on top of those and see what it looks
like.

Cheers,
Don
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/