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  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]
Date:	Sat, 19 May 2007 13:39:23 +0200 (CEST)
From:	Stefan Richter <>
To:	Linus Torvalds <>
Subject: [GIT PULL] ieee1394 fixes post 2.6.22-rc2

Linus, please pull from the for-linus branch at

    git:// for-linus

to receive the following IEEE 1394 subsystem updates:

  - fix regression in 2.6.22-rc1:
    raw1394 asynchronous transmit was broken

  - fix old bug in raw1394:
    32bit compat code for 64bit kernels was broken and incomplete

  - fix old eth1394 bug:
    packets were frequently dropped in transmit path
    (This fixes only the most common type of failure, tlabel exhaustion.)

  - trivial sbp2 fix

The 32bit compat code has been posted to LKML twice.  The rest was only
seen on linux1394-devel, hence I'll follow up with the combined diff.

 drivers/ieee1394/eth1394.c |   84 +++++++++++++-----
 drivers/ieee1394/eth1394.h |    4 +
 drivers/ieee1394/raw1394.c |  172 ++++++++++++++++++++++++++++--------
 drivers/ieee1394/sbp2.c    |    1 +
 4 files changed, 204 insertions(+), 57 deletions(-)

Petr Vandrovec (4):
      ieee1394: raw1394: Fix async send
      ieee1394: raw1394: Fix read() for 32bit userland on 64bit kernel
      ieee1394: raw1394: Fix write() for 32bit userland on 64bit kernel
      ieee1394: raw1394: Add ioctl() for 32bit userland on 64bit kernel

Stefan Richter (3):
      ieee1394: sbp2: include workqueue.h
      ieee1394: eth1394: remove bogus netif_wake_queue
      ieee1394: eth1394: handle tlabel exhaustion
Stefan Richter
-=====-=-=== -=-= =--==

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists