linux-kernel - Re: Linux v2.6.21-rc3

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: <m1zm6hq70n.fsf@ebiederm.dsl.xmission.com>
Date:	Tue, 13 Mar 2007 13:26:48 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...sta.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	David Miller <davem@...emloft.net>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: Linux v2.6.21-rc3


Here is a quick summary of the regressions I am looking at.

- Currently we appear to have a pid leak in tty_io.c
  http://lkml.org/lkml/2007/3/8/222

- There is a missing init_WORK in vt.c that cases oops
  when we attempt to use SAK.
  http://lkml.org/lkml/2007/3/11/148

- We have a network ABI regression caused by the latest sysfs
  changes to net-sysfs.c   In particular we now cannot rename network
  devices if our destination name happens to be the name of a sysfs file that
  the network device appears in, and if we try the kernel gets very
  confused and we loose access to the network device. 

  Do we just want to revert commit 43cb76d91ee85f579a69d42bc8efc08bac560278
  Greg has been working on this off and on and has not found a
  simple solution yet.

- pci_save_state, pci_restore_state are broken and have been for a
  while if used on anything besides plain pci (pci-x, pci-e and msi)
  and are not used in pairs. (gregkh and Andrew have the patches to 
  correct this).

- I am still confirming that I have fixed all of the irq handling
  problems that resulted in the "No irq for vector" message.  I think
  I have but I have at least one indirect bug report that I'm still
  following up on.

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