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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Sat, 04 Jan 2014 21:04:55 -0500 (EST)
From:	David Miller <>
Subject: [GIT] Sparc

Please pull to get these Sparc bug fixes:

1) Missing include can lead to build failure, from Kirill Tkhai.

2) Use dev_is_pci() where applicable, from Yijing Wang.

3) Enable irqs after we enable preemption in cpu startup path,
   from Kirill Tkhai.

4) Revert a __copy_{to,from}_user_inatomic change that broke
   iov_iter_copy_from_user_atomic() and thus several tests in
   xfstests and LTP.  From Dave Kleikamp.

Please pull, thanks a lot!

The following changes since commit dea4f48a0a301b23c65af8e4fe8ccf360c272fbf:

  Merge branch 'leds-fixes-for-3.13' of git:// (2013-12-02 12:08:01 -0800)

are available in the git repository at:

  git:// master

for you to fetch changes up to 16932237f2978a2265662f8de4af743b1f55a209:

  Revert "sparc64: Fix __copy_{to,from}_user_inatomic defines." (2014-01-04 17:55:19 -0800)

Dave Kleikamp (1):
      Revert "sparc64: Fix __copy_{to,from}_user_inatomic defines."

Kirill Tkhai (2):
      sparc64: Fix build regression
      sparc64: smp_callin: Enable irqs after preemption is disabled

Yijing Wang (1):
      sparc/PCI: Use dev_is_pci() to identify PCI devices

 arch/sparc/include/asm/uaccess_64.h | 4 ++--
 arch/sparc/kernel/iommu.c           | 2 +-
 arch/sparc/kernel/ioport.c          | 5 ++---
 arch/sparc/kernel/kgdb_64.c         | 1 +
 arch/sparc/kernel/smp_64.c          | 3 ++-
 5 files changed, 8 insertions(+), 7 deletions(-)
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