linux-kernel - Re: [PATCH 2/6] ipmi: Increase KCS timeouts

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: <20120203115026.9e2a357f.akpm@linux-foundation.org>
Date:	Fri, 3 Feb 2012 11:50:26 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Corey Minyard <cminyard@...sta.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	OpenIPMI Developers <openipmi-developer@...ts.sourceforge.net>,
	Matthew Garrett <mjg@...hat.com>
Subject: Re: [PATCH 2/6] ipmi: Increase KCS timeouts

On Fri, 03 Feb 2012 09:47:55 -0600
Corey Minyard <cminyard@...sta.com> wrote:

> From: Matthew Garrett <mjg@...hat.com>
> 
> We currently time out and retry KCS transactions after 1 second of waiting
> for IBF or OBF. This appears to be too short for some hardware. The IPMI
> spec says "All system software wait loops should include error timeouts. For
> simplicity, such timeouts are not shown explicitly in the flow diagrams. A
> five-second timeout or greater is recommended". Change the timeout to five
> seconds to satisfy the slow hardware.

Several of these patches fix bugs/problems, but there isn't enough info
here for me to decide whether we should patch 3.3 or earlier kernels. 
I'm assuming "3.4 only".

> From: Matthew Garrett <mjg@...hat.com>

A dupe.  The first one was correct.
--
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/