linux-kernel - [char-misc 0/4] mei: reset fix

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-next>] [day] [month] [year] [list]

Date:	Wed,  8 Jan 2014 20:19:20 +0200
From:	Tomas Winkler <tomas.winkler@...el.com>
To:	gregkh@...uxfoundation.org
Cc:	arnd@...db.de, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, Tomas Winkler <tomas.winkler@...el.com>
Subject: [char-misc 0/4] mei: reset fix

This series should address possible hiccup in
mei reset flow presenting itself as never ending   
repetition of error line.

unexpected reset: dev_state = RESETTING  

The patches make sure that stall watchdog doesn't jump in 
prior to its time; second the reset flow won't recuse,
and at last  it will allow no more than 3 consecutive resets
for misbehaving hardware.


Tomas Winkler (4):
  mei: do not run reset flow from the interrupt thread
  mei: use hbm idle state to prevent spurious resets
  mei: revamp mei reset state machine
  mei: limit the number of consecutive resets

 drivers/misc/mei/client.c    |   1 +
 drivers/misc/mei/hbm.c       | 221 ++++++++++++++++++++++------------
 drivers/misc/mei/hbm.h       |   7 +-
 drivers/misc/mei/hw-me.c     |  40 +++----
 drivers/misc/mei/init.c      | 280 +++++++++++++++++++++++++++----------------
 drivers/misc/mei/interrupt.c |  45 ++++---
 drivers/misc/mei/mei_dev.h   |  11 +-
 drivers/misc/mei/pci-me.c    |  10 +-
 8 files changed, 386 insertions(+), 229 deletions(-)

-- 
1.8.4.2

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