linux-kernel - Re: [PATCH 0/9] watchdog: internally split softlockup and hardlockup

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]

Message-Id: <20150205152230.e978767c9c5eeb3b97be99f8@linux-foundation.org>
Date:	Thu, 5 Feb 2015 15:22:30 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Don Zickus <dzickus@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/9] watchdog: internally split softlockup and
 hardlockup

On Thu,  5 Feb 2015 15:40:16 -0500 Don Zickus <dzickus@...hat.com> wrote:

> The hardlockup and softockup had always been tied together.  Due to the request
> of KVM folks, they had a need to have one enabled but not the other.
> Internally rework the code to split things apart more cleanly.
> 
> There is a bunch of churn here, but the end result should be code that should
> be easier to maintain and fix without knowing the internals of what is going
> on.

We're late in -rc7, which is not a good time for "a bunch of churn". 
So I'll park this series for consideration after 3.19 has been
released.  I'll let you know if it has seriously bitrotted by then.


--
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/