linux-kernel - [RFC PATCH 00/12] e1000e debug and protection patches

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:	Mon, 29 Sep 2008 20:19:16 -0700
From:	Jesse Brandeburg <jesse.brandeburg@...el.com>
To:	linux-kernel@...r.kernel.org
Cc:	linux-netdev@...r.kernel.org, kkeil@...e.de, agospoda@...hat.com,
	arjan@...ux.intel.com, david.graham@...el.com,
	bruce.w.allan@...el.com, jkosina@...e.cz, john.ronciak@...el.com,
	tglx@...utronix.de, chris.jones@...onical.com,
	tim.gardner@...el.com, airlied@...il.com
Subject: [RFC PATCH 00/12] e1000e debug and protection patches

please be warned this is a test series of patches that we are currently
validating, but we wanted to post them sooner than later. this series of
patches implements:

1-2) base kernel code fixes that might be helpful for debugging
3-6) a series of patches to fix some (possible) buglets in eeprom access code
7) a patch that triggered the bugs that were fixed in 3-6, from Thomas
8-9) (what should be) debug helper patches for testers to log to syslog the
     first bytes of the eeprom, that are checksummed at least.
10) protect iomapped memory from write by kernel processes
11) write protect the actual e1000e flash space, add module param to disable[1]
12) update the version so we can tell we're running with this test driver.

# This series applies on GIT commit eaf9e45100b56c18a2236464cadd92d9a3d399ea

Tomorrow we should be able to test and post the eeprom restore patches for
the driver.

[1]  we will follow up tomorrow with a patch that locks the actual flash AND
     the bits used by 11) that requires a full chip reset to unlock, as
     we see a possible way that the iomapped registers could still be poked
     in such a way to unlock the flash space.

I will probably update these again but they seem to work for now.

---

Bruce Allan (3):
      e1000e: write protect ICHx NVM to prevent malicious write/erase
      e1000e: Use set_memory_ro()/set_memory_rw() to protect flash memory
      x86: export set_memory_ro and set_memory_rw

Jesse Barnes (1):
      pci sysfs warning

Jesse Brandeburg (7):
      update version
      e1000e: dump eeprom to dmesg for ich8/9
      e1000e: allow bad checksum
      e1000e: drop stats lock
      e1000e: fix lockdep issues
      e1000e: do not ever sleep in interrupt context
      e1000e: reset swflag after resetting hardware

Thomas Gleixner (1):
      e1000e: debug contention on NVM SWFLAG


 arch/x86/mm/pageattr.c       |    2 +
 drivers/net/e1000e/e1000.h   |    6 +-
 drivers/net/e1000e/ethtool.c |    9 ++
 drivers/net/e1000e/hw.h      |    1 
 drivers/net/e1000e/ich8lan.c |   82 +++++++++++++++++++++
 drivers/net/e1000e/netdev.c  |  167 ++++++++++++++++++++++++++++--------------
 drivers/net/e1000e/param.c   |   30 ++++++++
 drivers/pci/pci-sysfs.c      |   14 ++++
 8 files changed, 255 insertions(+), 56 deletions(-)

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