opensuse:kernel.git
4 years agoRefresh patches.suse/mm-speedup-in-__early_pfn_to_nid.patch.
Michal Hocko [Mon, 22 Apr 2013 15:55:27 +0000 (17:55 +0200)]
Refresh patches.suse/mm-speedup-in-__early_pfn_to_nid.patch.

suse-commit: 8e590604f08ae4a82d7a92b82207c688eb3764e7

4 years agoMerge branch 'SLE11-SP2' into SLE11-SP3
Michal Marek [Mon, 22 Apr 2013 15:18:38 +0000 (17:18 +0200)]
Merge branch 'SLE11-SP2' into SLE11-SP3

Dropped all SP2 changes in Xen and Btrfs.

Conflicts:
kernel-source.changes
patches.suse/btrfs-*
patches.xen/*
series.conf

suse-commit: f4c453d306e40ebfa3e65b54bcd6fff3090ddf94

4 years agomm: speedup in __early_pfn_to_nid (bnc#810624).
Michal Hocko [Mon, 22 Apr 2013 14:54:58 +0000 (16:54 +0200)]
mm: speedup in __early_pfn_to_nid (bnc#810624).

suse-commit: 5742adf34b1bb49e0f5fc3faeda9e778cb46ac90

4 years agoMerge branch 'SLE11-SP2-3.0-stable-respin' into SLE11-SP2
Jiri Kosina [Mon, 22 Apr 2013 13:54:20 +0000 (15:54 +0200)]
Merge branch 'SLE11-SP2-3.0-stable-respin' into SLE11-SP2

suse-commit: 8a408bcd3d8bc15d6e5d13406c55f835f3f388e7

4 years ago- patches.kernel.org/0011-Revert-sysfs-fix-race-between-readdir-and-lseek.patch:
Jiri Kosina [Mon, 22 Apr 2013 13:28:29 +0000 (15:28 +0200)]
- patches./0011-Revert-sysfs-fix-race-between-readdir-and-lseek.patch:
  [PATCH 3.0-stable] Revert "sysfs: fix race between readdir
  and lseek" (bnc#816443).

suse-commit: 342df61115686fa42e28efdf6292dc6ab578cd8c

4 years ago- patches.suse/Revert-8021q-fix-a-potential-use-after-free.patch:
Michal Kubecek [Mon, 22 Apr 2013 13:03:19 +0000 (15:03 +0200)]
- patches.suse/Revert-8021q-fix-a-potential-use-after-free.patch:
  Revert "8021q: fix a potential use-after-free".

suse-commit: da20808d47b34da461403e6505a3bd64c89c25cf

4 years agoMerge branch 'SLE11-SP3-3.0-stable-respin' of /labs/jkosina/src/suse-kernel-source...
Jiri Kosina [Mon, 22 Apr 2013 13:45:00 +0000 (15:45 +0200)]
Merge branch 'SLE11-SP3-3.0-stable-respin' of /labs/jkosina/src/suse-kernel-source into SLE11-SP3

suse-commit: b055bf46b9a80c2054180a72b8c18382bc905e05

4 years ago[PATCH 3.0-stable] Revert "sysfs: fix race between readdir
Jiri Kosina [Mon, 22 Apr 2013 13:23:53 +0000 (15:23 +0200)]
[PATCH 3.0-stable] Revert "sysfs: fix race between readdir
and lseek" (bnc#816443).

suse-commit: d484b0117fd3a513df6ad8978234778de749c898

4 years agoRevert "8021q: fix a potential use-after-free".
Michal Kubecek [Mon, 22 Apr 2013 13:09:34 +0000 (15:09 +0200)]
Revert "8021q: fix a potential use-after-free".

suse-commit: 10b1a250c519ba19711e985aaeddcfa42435c4b5

4 years ago- Update config files.
Lee, Chun-Yi [Mon, 22 Apr 2013 13:33:00 +0000 (21:33 +0800)]
- Update config files.
- Refresh
  add 'CONFIG_UCS2_STRING=y' to following config files:
  config/i386/debug
  config/i386/default
  config/i386/pae
  config/i386/trace
  config/ia64/debug
  config/ia64/default
  config/ia64/trace
  config/x86_64/debug
  config/x86_64/default
  config/x86_64/trace
  config/x86_64/xen
  patches.fixes/0003-crypto-GnuPG-based-MPI-lib-make-files-part-3.patch.
- Refresh
  patches.fixes/0011-X.509-Implement-simple-static-OID-registry.patch.
- Refresh
  patches.suse/0008_efi_Enable_secure_boot_lockdown_automatically_when_enabled_in_firmware_v2.patch.
- Refresh patches.xen/xen-x86-EFI.
- Refresh patches.xen/xen3-auto-xen-kconfig.diff.

suse-commit: 06044e05573156b6c51cc0c94c1178523f8f986c

4 years agox86,efi: Implement efi_no_storage_paranoia parameter
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
x86,efi: Implement efi_no_storage_paranoia parameter
(fate#314499, fate#314509).

suse-commit: 279a66880a9ebe895a735d83643317a6e47e2718
Note: This patch series did not apply

4 years agoefi: Export efi_query_variable_store() for efivars.ko
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
efi: Export efi_query_variable_store() for efivars.ko
(fate#314499, fate#314509).

suse-commit: 39a5bf4e67ee626d3fe39c753131da9357868421
Note: This patch series did not apply

4 years agox86/Kconfig: Make EFI select UCS2_STRING (fate#314499,
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
x86/Kconfig: Make EFI select UCS2_STRING (fate#314499,
fate#314509).

suse-commit: 2316da78a608ec507ce69804d520bccbd4d50873
Note: This patch series did not apply

4 years agoefi: Distinguish between "remaining space" and actually used
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
efi: Distinguish between "remaining space" and actually used
space (fate#314499, fate#314509).

suse-commit: ca37e7e8dc8adeb8a1989661ab5ba80f9660c4da
Note: This patch series did not apply

4 years agoefi: Pass boot services variable info to runtime code
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
efi: Pass boot services variable info to runtime code
(fate#314499, fate#314509).

suse-commit: b0b28b77a7418ae50c3783bf6d886d50d0a96e82
Note: This patch series did not apply

4 years agoMove utf16 functions to kernel core and rename (fate#314499,
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
Move utf16 functions to kernel core and rename (fate#314499,
fate#314509,).

suse-commit: e56f5252105691fc0308ec433ec700688d2a9888
Note: This patch series did not apply

4 years agox86,efi: Check max_size only if it is non-zero (fate#314499,
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
x86,efi: Check max_size only if it is non-zero (fate#314499,
fate#314509).

suse-commit: 435dc5ef5ec4c88414687edb12f8ea41c57e2763

4 years agox86, efivars: firmware bug workarounds should be in platform
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
x86, efivars: firmware bug workarounds should be in platform
code (fate#314499, fate#314509).

suse-commit: c9fe293ccad6a02743e5f05e098ec21c7576ef5e

4 years agox86, efi: Set runtime_version to the EFI spec revision
Lee, Chun-Yi [Mon, 22 Apr 2013 13:32:35 +0000 (21:32 +0800)]
x86, efi: Set runtime_version to the EFI spec revision
(fate#314499, fate#314509).

suse-commit: 0f33512601a94d3fee3d71d8930206eceb24997f

4 years ago- patches.kernel.org/0011-Revert-sysfs-fix-race-between-readdir-and-lseek.patch:
Jiri Kosina [Mon, 22 Apr 2013 13:28:29 +0000 (15:28 +0200)]
- patches./0011-Revert-sysfs-fix-race-between-readdir-and-lseek.patch:
  [PATCH 3.0-stable] Revert "sysfs: fix race between readdir
  and lseek" (bnc#816443).

suse-commit: 0c871024a9bb2ede41c9919f120c5dd36ca960db

4 years ago[PATCH 3.0-stable] Revert "sysfs: fix race between readdir
Jiri Kosina [Mon, 22 Apr 2013 13:23:53 +0000 (15:23 +0200)]
[PATCH 3.0-stable] Revert "sysfs: fix race between readdir
and lseek" (bnc#816443).

suse-commit: 7dd2e1e18ee591984e60ed3a1d0f8978436057f3

4 years agoRevert "8021q: fix a potential use-after-free".
Michal Kubecek [Mon, 22 Apr 2013 13:09:34 +0000 (15:09 +0200)]
Revert "8021q: fix a potential use-after-free".

suse-commit: 275a37de7fae6180ef75935cba80d5bfb985cf1f

4 years ago- patches.suse/Revert-8021q-fix-a-potential-use-after-free.patch:
Michal Kubecek [Mon, 22 Apr 2013 13:03:19 +0000 (15:03 +0200)]
- patches.suse/Revert-8021q-fix-a-potential-use-after-free.patch:
  Revert "8021q: fix a potential use-after-free".

suse-commit: 5d9aa022ef9ba50b1332804641f2138cc748c348

4 years agosupported.conf: Added missing deps for pNFS.
Jeff Mahoney [Mon, 22 Apr 2013 00:11:58 +0000 (20:11 -0400)]
supported.conf: Added missing deps for pNFS.

suse-commit: e509b5049fc173f758ae07f341426771b520572b

4 years agosupported.conf: added pNFS modules (bnc#811085).
Jeff Mahoney [Sun, 21 Apr 2013 19:03:36 +0000 (15:03 -0400)]
supported.conf: added pNFS modules (bnc#811085).

suse-commit: 0a87c7709d349e8b48114270bee755308d38d94d

4 years ago- patches.suse/btrfs-1013-don-t-re-enter-when-allocating-a-chunk.patch:
David Sterba [Thu, 18 Apr 2013 14:05:34 +0000 (16:05 +0200)]
- patches.suse/btrfs-1013-don-t-re-enter-when-allocating-a-chunk.patch:
  Btrfs: don't re-enter when allocating a chunk (FATE#312888).
- patches.suse/btrfs-1019-save-us-a-read_lock.patch: Btrfs:
  save us a read_lock (FATE#312888).
- patches.suse/btrfs-1026-Check-CAP_DAC_READ_SEARCH-for-btrfs_IOC_INO_PA.patch:
  Btrfs: Check CAP_DAC_READ_SEARCH for BTRFS_IOC_INO_PATHS
  (FATE#312888).
- patches.suse/btrfs-1038-remove-unused-fs_info-from-btrfs_decode_error.patch:
  btrfs: remove unused fs_info from btrfs_decode_error()
  (FATE#312888).
- patches.suse/btrfs-1039-handle-null-fs_info-in-btrfs_panic.patch:
  btrfs: handle null fs_info in btrfs_panic() (FATE#312888).
- patches.suse/btrfs-1042-fix-varargs-in-__btrfs_std_error.patch:
  btrfs: fix varargs in __btrfs_std_error (FATE#312888).
- patches.suse/btrfs-1056-fix-the-race-between-bio-and-btrfs_stop_worker.patch:
  Btrfs: fix the race between bio and btrfs_stop_workers
  (FATE#312888).
- patches.suse/btrfs-1097-fix-NULL-pointer-after-aborting-a-transaction.patch:
  Btrfs: fix NULL pointer after aborting a transaction
  (FATE#312888).
- patches.suse/btrfs-8195-fix-infinite-loop-when-we-abort-on-mount.patch:
  Btrfs: fix infinite loop when we abort on mount.

suse-commit: 4f6bbabd59f3429ac016809aabca1e79f861a072

4 years ago- Update Xen patches to 3.0.74.
Jan Beulich [Fri, 19 Apr 2013 08:30:06 +0000 (10:30 +0200)]
- Update Xen patches to 3.0.74.

suse-commit: 95326c5b9924b8525682f652e90dcde42ccba6ad

4 years agoqlcnic: Bump up the version to 5.1.38 (bnc#804494).
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
qlcnic: Bump up the version to 5.1.38 (bnc#804494).

suse-commit: 52d44dac0055e12fea5a7e2b410771df0f2ca543

4 years agoqlcnic: Clear link status when interface is down (bnc#804494).
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
qlcnic: Clear link status when interface is down (bnc#804494).

suse-commit: 5990bdb3093d77668d55f0728fd4f799587ca44e

4 years agoqlcnic: change mdelay to msleep (bnc#804494).
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
qlcnic: change mdelay to msleep (bnc#804494).

suse-commit: b041586e6be79bd3428de15d27233e7f35e2d205

4 years agoqlcnic: Log warning message for 83xx adapter in MSI mode
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
qlcnic: Log warning message for 83xx adapter in MSI mode
(bnc#804494).

suse-commit: bdc410840f7a69001eb9e5901fb26e14be8e5d14

4 years agoqlcnic: Fix configure mailbox interrupt command for 83xx adapter
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
qlcnic: Fix configure mailbox interrupt command for 83xx adapter
(bnc#804494).

suse-commit: c2a28bc0f0393579839f146f3a3ac3b758c01bea

4 years agodrivers:net: dma_alloc_coherent: use __GFP_ZERO instead of
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
drivers:net: dma_alloc_coherent: use __GFP_ZERO instead of
memset(, 0) (bnc#804494).

suse-commit: fc2d328a23d665fd615bef94461789eaac11100c

4 years agodriver/qlogic: replace ip_fast_csum with csum_replace2
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
driver/qlogic: replace ip_fast_csum with csum_replace2
(bnc#804494).

suse-commit: bfff9ec37dee7e6c9c519b121fa8da3cbce6ad0a

4 years agodrivers:net: Remove dma_alloc_coherent OOM messages
Benjamin Poirier [Thu, 18 Apr 2013 19:24:10 +0000 (15:24 -0400)]
drivers:net: Remove dma_alloc_coherent OOM messages
(bnc#804494).

suse-commit: 13183f49d7925d76c6d3df9a607089a1236ce405

4 years ago- patches.suse/btrfs-8024-workaround-for-cleaner-deadlock.patch: Delete.
David Sterba [Thu, 18 Apr 2013 13:15:14 +0000 (15:15 +0200)]
- patches.suse/btrfs-8024-workaround-for-cleaner-deadlock.patch: Delete.
- patches.suse/btrfs-8077-stop-defrag-the-files-automatically-when-doin-.patch:
  Refresh.
- patches.suse/btrfs-8094-flush-all-the-dirty-pages-if-try_to_writeback_.patch:
  Refresh.
- patches.suse/btrfs-8095-use-writeback_inodes_sb-_nr-_if_idle.patch:
  Refresh.

suse-commit: ec6129fc0752a429425ed22cd742cc07d5615141

4 years ago- patches.suse/btrfs-0992-don-t-try-to-notify-udev-about-missing-devices.patch:
David Sterba [Thu, 18 Apr 2013 12:43:02 +0000 (14:43 +0200)]
- patches.suse/btrfs-0992-don-t-try-to-notify-udev-about-missing-devices.patch:
  btrfs: don't try to notify udev about missing devices
  (FATE#312888).
- patches.suse/btrfs-1064-add-cancellation-points-to-defrag.patch:
  btrfs: add cancellation points to defrag (FATE#312888).
- patches.suse/btrfs-1072-define-btrfs_MAGIC-as-a-u64-value.patch:
  btrfs: define BTRFS_MAGIC as a u64 value (FATE#312888).
- patches.suse/btrfs-1089-make-sure-NODATACOW-also-gets-NODATASUM-set.patch:
  Btrfs: make sure NODATACOW also gets NODATASUM set
  (FATE#312888).
- patches.suse/btrfs-1110-enforce-min_bytes-parameter-during-extent-allo.patch:
  Btrfs: enforce min_bytes parameter during extent allocation
  (FATE#312888).
- patches.suse/btrfs-1116-build-up-error-handling-for-merge_reloc_roots.patch:
  Btrfs: build up error handling for merge_reloc_roots
  (FATE#312888).
- patches.suse/btrfs-1117-free-all-recorded-tree-blocks-on-error.patch:
  Btrfs: free all recorded tree blocks on error (FATE#312888).
- patches.suse/btrfs-1118-do-not-BUG_ON-in-prepare_to_reloc.patch:
  Btrfs: do not BUG_ON in prepare_to_reloc (FATE#312888).
- patches.suse/btrfs-1119-do-not-BUG_ON-on-aborted-situation.patch:
  Btrfs: do not BUG_ON on aborted situation (FATE#312888).
- patches.suse/btrfs-1130-handle-a-bogus-chunk-tree-nicely.patch:
  Btrfs: handle a bogus chunk tree nicely (FATE#312888).
- patches.suse/btrfs-1143-don-t-drop-path-when-printing-out-tree-errors-.patch:
  Btrfs: don't drop path when printing out tree errors in scrub
  (FATE#312888).
- patches.suse/btrfs-8194-make-subvol-creation-deletion-killable-in-the-.patch:
  btrfs: make subvol creation/deletion killable in the early
  stages.
- patches.suse/btrfs-8204-abort-unlink-trans-in-missed-error-case.patch:
  btrfs: abort unlink trans in missed error case.
- patches.suse/btrfs-8213-fix-reada-debug-code-compilation.patch:
  Btrfs: fix reada debug code compilation.
- patches.suse/btrfs-8214-return-error-when-we-specify-wrong-start-to-de.patch:
  Btrfs: return error when we specify wrong start to defrag.
- patches.suse/btrfs-8215-don-t-force-pages-under-writeback-to-finish-wh.patch:
  Btrfs: don't force pages under writeback to finish when
  aborting.

suse-commit: d4f29b95b5c853f7f4a140edfddf365e6f8126ce

4 years ago- Linux 3.0.74.
Jiri Slaby [Wed, 17 Apr 2013 12:27:23 +0000 (14:27 +0200)]
- Linux 3.0.74.
- patches.kabi/revert-x86-mm-Patch-out-arch_flush_lazy_mmu_mode-whe.patch:
  Revert "x86, mm: Patch out arch_flush_lazy_mmu_mode() when
  running on bare metal".

suse-commit: 49c673d245005aa19aaedf0b9d25aa8298a928e4

4 years ago- Linux 3.0.73.
Jiri Slaby [Wed, 17 Apr 2013 11:57:20 +0000 (13:57 +0200)]
- Linux 3.0.73.
- patches.suse/kdump-x86-remap-allocator: Delete.

suse-commit: 02bd848e9a7b65e457eccfa3f3dfaba58679c34c

4 years ago- Linux 3.0.72 (CVE-2010-3873 CVE-2011-4131 CVE-2011-4604 CVE-2011-4622
Jiri Slaby [Wed, 17 Apr 2013 11:42:20 +0000 (13:42 +0200)]
- Linux 3.0.72 (CVE-2010-3873 CVE-2011-4131 CVE-2011-4604 CVE-2011-4622
  CVE-2012-1601 CVE-2012-2119 CVE-2012-2137 CVE-2012-4461 CVE-2012-5517
  bnc#651219 bnc#730117 bnc#736149 bnc#738210 bnc#754898 bnc#758243
  bnc#767612 bnc#787821 bnc#789235).
- patches.kabi/kabi-protect-struct-tracer.patch: kABI: protect
  struct tracer.
- patches.arch/005-efi_pstore_fixes.patch: Refresh.
- patches.drivers/0001-add-firmware-update-for-Atheros-0cf3-311f.patch:
  Refresh.
- patches.drivers/0001-enable-Atheros-0cf3-311e-for-firmware-upload.patch:
  Refresh.
- patches.suse/btrfs-0448-fix-block_rsv-and-space_info-lock-ordering.patch:
  Refresh.
- patches.drivers/drm-i915-don-t-set-unpin_work-if-vblank_get-fails:
  Delete.
- patches.fixes/batman-adv-Only-write-requested-number-of-byte-to-us.patch:
  Delete.
- patches.fixes/batman-adv-bat_socket_read-missing-checks.patch:
  Delete.
- patches.fixes/kvm-KVM-Clean-up-error-handling-during-VCPU-creation.patch:
  Delete.
- patches.fixes/kvm-KVM-Ensure-all-vcpus-are-consistent-with-in-kernel-i.patch:
  Delete.
- patches.fixes/kvm-KVM-x86-Prevent-starting-PIT-timers-in-the-absence-o.patch:
  Delete.
- patches.fixes/kvm-invalid-opcode-oops-on-SET_SREGS-with-OSXSAVE-bi.patch:
  Delete.
- patches.fixes/kvm-set-irq.patch: Delete.
- patches.fixes/macvtap-zerocopy-validate-vectors-before-building-sk.patch:
  Delete.
- patches.fixes/mm-hotplug-correctly-add-zone-to-other-nodes-list.patch:
  Delete.
- patches.fixes/nfs-bitmap-fix-fix: Delete.
- patches.fixes/nfs-bitmap-size.fix: Delete.
- patches.fixes/x25-Handle-undersized-fragmented-skbs.patch:
  Delete.
- patches.fixes/x25-Validate-incoming-call-user-data-lengths.patch:
  Delete.
- patches.rpmify/ia64-sa_restorer-fix.patch: Delete.

suse-commit: 0a5a5d8832d2bc274b3850fe88fd030afde0c421

4 years ago- Linux 3.0.72 (CVE-2010-3873 CVE-2011-4131 CVE-2011-4604 CVE-2011-4622
Jiri Slaby [Wed, 17 Apr 2013 11:02:21 +0000 (13:02 +0200)]
- Linux 3.0.72 (CVE-2010-3873 CVE-2011-4131 CVE-2011-4604 CVE-2011-4622
  CVE-2012-1601 CVE-2012-2119 CVE-2012-2137 CVE-2012-4461 CVE-2012-5517
  bnc#651219 bnc#730117 bnc#736149 bnc#738210 bnc#754898 bnc#758243
  bnc#767612 bnc#787821 bnc#789235).
- patches.arch/005-efi_pstore_fixes.patch: Refresh.
- patches.drivers/0001-add-firmware-update-for-Atheros-0cf3-311f.patch:
  Refresh.
- patches.drivers/0001-enable-Atheros-0cf3-311e-for-firmware-upload.patch:
  Refresh.
- patches.suse/btrfs-0448-fix-block_rsv-and-space_info-lock-ordering.patch:
  Refresh.
- patches.drivers/drm-i915-don-t-set-unpin_work-if-vblank_get-fails:
  Delete.
- patches.fixes/batman-adv-Only-write-requested-number-of-byte-to-us.patch:
  Delete.
- patches.fixes/batman-adv-bat_socket_read-missing-checks.patch:
  Delete.
- patches.fixes/kvm-KVM-Clean-up-error-handling-during-VCPU-creation.patch:
  Delete.
- patches.fixes/kvm-KVM-Ensure-all-vcpus-are-consistent-with-in-kernel-i.patch:
  Delete.
- patches.fixes/kvm-KVM-x86-Prevent-starting-PIT-timers-in-the-absence-o.patch:
  Delete.
- patches.fixes/kvm-invalid-opcode-oops-on-SET_SREGS-with-OSXSAVE-bi.patch:
  Delete.
- patches.fixes/kvm-set-irq.patch: Delete.
- patches.fixes/macvtap-zerocopy-validate-vectors-before-building-sk.patch:
  Delete.
- patches.fixes/mm-hotplug-correctly-add-zone-to-other-nodes-list.patch:
  Delete.
- patches.fixes/nfs-bitmap-fix-fix: Delete.
- patches.fixes/nfs-bitmap-size.fix: Delete.
- patches.fixes/x25-Handle-undersized-fragmented-skbs.patch:
  Delete.
- patches.fixes/x25-Validate-incoming-call-user-data-lengths.patch:
  Delete.
- patches.rpmify/ia64-sa_restorer-fix.patch: Delete.

suse-commit: c54bdef1a8902ecbdcfe6dc029373b385edc5bf0

4 years agomissed one hash -> hash.w change
Torsten Duwe [Wed, 17 Apr 2013 16:49:07 +0000 (18:49 +0200)]
missed one hash -> hash.w change

suse-commit: 64779069a5161e6ff02036c470222a5484e742d9

4 years ago- patches.suse/revert-some-random-changes: /dev/urandom returning
Torsten Duwe [Wed, 17 Apr 2013 16:01:57 +0000 (18:01 +0200)]
- patches.suse/revert-some-random-changes: /dev/urandom returning
  EOF: trim down revert to not change kabi. (bnc#789359).

suse-commit: 2510012faef99c7e86ddec742ea8805a66e4ee5a

4 years ago- patches.drivers/alsa-sp3-pre-695-Yet-another-fix-for-broken-HSW-HDMI-pin:
Takashi Iwai [Wed, 17 Apr 2013 13:13:39 +0000 (15:13 +0200)]
- patches.drivers/alsa-sp3-pre-695-Yet-another-fix-for-broken-HSW-HDMI-pin:
  Refresh.  Fix the invalid PCI SSID check (bnc#806404)

suse-commit: d0d18112e6f72394132628ceee18e0d3e5b48df9

4 years ago- patches.fixes/tun-reserves-space-for-network-in-skb.patch:
Michal Kubecek [Wed, 17 Apr 2013 12:43:28 +0000 (14:43 +0200)]
- patches.fixes/tun-reserves-space-for-network-in-skb.patch:
  tun: reserves space for network in skb (bnc#803394).

suse-commit: e0913c718b80459269abc301bc59279cb0941c33

4 years agoremove one hunk already included in kABI fixup
Torsten Duwe [Wed, 17 Apr 2013 10:34:22 +0000 (12:34 +0200)]
remove one hunk already included in kABI fixup

suse-commit: a5dfe550b8fbdf730d6bba0b2ebb0fb9270dcd48

4 years ago- patches.suse/revert-tytsos-random-changes: /dev/urandom
Torsten Duwe [Wed, 17 Apr 2013 10:20:37 +0000 (12:20 +0200)]
- patches.suse/revert-tytsos-random-changes: /dev/urandom
  returning EOF (bnc#89359).

suse-commit: 209e1d955fdb67ba21279798c356faef2b11d542
Note: This patch series did not apply

4 years agoLinux 3.0.74
Greg Kroah-Hartman [Wed, 17 Apr 2013 04:17:25 +0000 (21:17 -0700)]
Linux 3.0.74

4 years agomtd: Disable mtdchar mmap on MMU systems
David Woodhouse [Tue, 9 Oct 2012 14:08:10 +0000 (15:08 +0100)]
mtd: Disable mtdchar mmap on MMU systems

commit f5cf8f07423b2677cebebcebc863af77223a4972 upstream.

This code was broken because it assumed that all MTD devices were map-based.
Disable it for now, until it can be fixed properly for the next merge window.

Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agor8169: fix auto speed down issue
Hayes Wang [Sat, 13 Apr 2013 10:26:55 +0000 (12:26 +0200)]
r8169: fix auto speed down issue

commit e2409d83434d77874b461b78af6a19cd6e6a1280 upstream.

It would cause no link after suspending or shutdowning when the
nic changes the speed to 10M and connects to a link partner which
forces the speed to 100M.

Check the link partner ability to determine which speed to set.

The link speed down code path is not factored in this kernel version.

Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Acked-by: Francois Romieu <romieu@fr.zoreil.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agomtdchar: fix offset overflow detection
Linus Torvalds [Sat, 8 Sep 2012 19:57:30 +0000 (12:57 -0700)]
mtdchar: fix offset overflow detection

commit 9c603e53d380459fb62fec7cd085acb0b74ac18f upstream.

Sasha Levin has been running trinity in a KVM tools guest, and was able
to trigger the BUG_ON() at arch/x86/mm/pat.c:279 (verifying the range of
the memory type).  The call trace showed that it was mtdchar_mmap() that
created an invalid remap_pfn_range().

The problem is that mtdchar_mmap() does various really odd and subtle
things with the vma page offset etc, and uses the wrong types (and the
wrong overflow) detection for it.

For example, the page offset may well be 32-bit on a 32-bit
architecture, but after shifting it up by PAGE_SHIFT, we need to use a
potentially 64-bit resource_size_t to correctly hold the full value.

Also, we need to check that the vma length plus offset doesn't overflow
before we check that it is smaller than the length of the mtdmap region.

This fixes things up and tries to make the code a bit easier to read.

Reported-and-tested-by: Sasha Levin <levinsasha928@gmail.com>
Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
Acked-by: Artem Bityutskiy <dedekind1@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ben Hutchings <ben@decadent.org.uk>
Cc: Brad Spengler <spender@grsecurity.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agox86, mm: Patch out arch_flush_lazy_mmu_mode() when running on bare metal
Boris Ostrovsky [Sat, 23 Mar 2013 13:36:36 +0000 (09:36 -0400)]
x86, mm: Patch out arch_flush_lazy_mmu_mode() when running on bare metal

commit 511ba86e1d386f671084b5d0e6f110bb30b8eeb2 upstream.

Invoking arch_flush_lazy_mmu_mode() results in calls to
preempt_enable()/disable() which may have performance impact.

Since lazy MMU is not used on bare metal we can patch away
arch_flush_lazy_mmu_mode() so that it is never called in such
environment.

[ hpa: the previous patch "Fix vmalloc_fault oops during lazy MMU
  updates" may cause a minor performance regression on
  bare metal.  This patch resolves that performance regression.  It is
  somewhat unclear to me if this is a good -stable candidate. ]

Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Link: http://lkml.kernel.org/r/1364045796-10720-2-git-send-email-konrad.wilk@oracle.com
Tested-by: Josh Boyer <jwboyer@redhat.com>
Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Acked-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agox86, mm, paravirt: Fix vmalloc_fault oops during lazy MMU updates
Samu Kallio [Sat, 23 Mar 2013 13:36:35 +0000 (09:36 -0400)]
x86, mm, paravirt: Fix vmalloc_fault oops during lazy MMU updates

commit 1160c2779b826c6f5c08e5cc542de58fd1f667d5 upstream.

In paravirtualized x86_64 kernels, vmalloc_fault may cause an oops
when lazy MMU updates are enabled, because set_pgd effects are being
deferred.

One instance of this problem is during process mm cleanup with memory
cgroups enabled. The chain of events is as follows:

- zap_pte_range enables lazy MMU updates
- zap_pte_range eventually calls mem_cgroup_charge_statistics,
  which accesses the vmalloc'd mem_cgroup per-cpu stat area
- vmalloc_fault is triggered which tries to sync the corresponding
  PGD entry with set_pgd, but the update is deferred
- vmalloc_fault oopses due to a mismatch in the PUD entries

The OOPs usually looks as so:

------------[ cut here ]------------
kernel BUG at arch/x86/mm/fault.c:396!
invalid opcode: 0000 [#1] SMP
.. snip ..
CPU 1
Pid: 10866, comm: httpd Not tainted 3.6.10-4.fc18.x86_64 #1
RIP: e030:[<ffffffff816271bf>]  [<ffffffff816271bf>] vmalloc_fault+0x11f/0x208
.. snip ..
Call Trace:
 [<ffffffff81627759>] do_page_fault+0x399/0x4b0
 [<ffffffff81004f4c>] ? xen_mc_extend_args+0xec/0x110
 [<ffffffff81624065>] page_fault+0x25/0x30
 [<ffffffff81184d03>] ? mem_cgroup_charge_statistics.isra.13+0x13/0x50
 [<ffffffff81186f78>] __mem_cgroup_uncharge_common+0xd8/0x350
 [<ffffffff8118aac7>] mem_cgroup_uncharge_page+0x57/0x60
 [<ffffffff8115fbc0>] page_remove_rmap+0xe0/0x150
 [<ffffffff8115311a>] ? vm_normal_page+0x1a/0x80
 [<ffffffff81153e61>] unmap_single_vma+0x531/0x870
 [<ffffffff81154962>] unmap_vmas+0x52/0xa0
 [<ffffffff81007442>] ? pte_mfn_to_pfn+0x72/0x100
 [<ffffffff8115c8f8>] exit_mmap+0x98/0x170
 [<ffffffff810050d9>] ? __raw_callee_save_xen_pmd_val+0x11/0x1e
 [<ffffffff81059ce3>] mmput+0x83/0xf0
 [<ffffffff810624c4>] exit_mm+0x104/0x130
 [<ffffffff8106264a>] do_exit+0x15a/0x8c0
 [<ffffffff810630ff>] do_group_exit+0x3f/0xa0
 [<ffffffff81063177>] sys_exit_group+0x17/0x20
 [<ffffffff8162bae9>] system_call_fastpath+0x16/0x1b

Calling arch_flush_lazy_mmu_mode immediately after set_pgd makes the
changes visible to the consistency checks.

RedHat-Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=914737
Tested-by: Josh Boyer <jwboyer@redhat.com>
Reported-and-Tested-by: Krishna Raman <kraman@redhat.com>
Signed-off-by: Samu Kallio <samu.kallio@aberdeencloud.com>
Link: http://lkml.kernel.org/r/1364045796-10720-1-git-send-email-konrad.wilk@oracle.com
Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agosched_clock: Prevent 64bit inatomicity on 32bit systems
Thomas Gleixner [Sat, 6 Apr 2013 08:10:27 +0000 (10:10 +0200)]
sched_clock: Prevent 64bit inatomicity on 32bit systems

commit a1cbcaa9ea87b87a96b9fc465951dcf36e459ca2 upstream.

The sched_clock_remote() implementation has the following inatomicity
problem on 32bit systems when accessing the remote scd->clock, which
is a 64bit value.

CPU0 CPU1

sched_clock_local() sched_clock_remote(CPU0)
...
remote_clock = scd[CPU0]->clock
    read_low32bit(scd[CPU0]->clock)
cmpxchg64(scd->clock,...)
    read_high32bit(scd[CPU0]->clock)

While the update of scd->clock is using an atomic64 mechanism, the
readout on the remote cpu is not, which can cause completely bogus
readouts.

It is a quite rare problem, because it requires the update to hit the
narrow race window between the low/high readout and the update must go
across the 32bit boundary.

The resulting misbehaviour is, that CPU1 will see the sched_clock on
CPU1 ~4 seconds ahead of it's own and update CPU1s sched_clock value
to this bogus timestamp. This stays that way due to the clamping
implementation for about 4 seconds until the synchronization with
CLOCK_MONOTONIC undoes the problem.

The issue is hard to observe, because it might only result in a less
accurate SCHED_OTHER timeslicing behaviour. To create observable
damage on realtime scheduling classes, it is necessary that the bogus
update of CPU1 sched_clock happens in the context of an realtime
thread, which then gets charged 4 seconds of RT runtime, which results
in the RT throttler mechanism to trigger and prevent scheduling of RT
tasks for a little less than 4 seconds. So this is quite unlikely as
well.

The issue was quite hard to decode as the reproduction time is between
2 days and 3 weeks and intrusive tracing makes it less likely, but the
following trace recorded with trace_clock=global, which uses
sched_clock_local(), gave the final hint:

  <idle>-0   0d..30 400269.477150: hrtimer_cancel: hrtimer=0xf7061e80
  <idle>-0   0d..30 400269.477151: hrtimer_start:  hrtimer=0xf7061e80 ...
irq/20-S-587 1d..32 400273.772118: sched_wakeup:   comm= ... target_cpu=0
  <idle>-0   0dN.30 400273.772118: hrtimer_cancel: hrtimer=0xf7061e80

What happens is that CPU0 goes idle and invokes
sched_clock_idle_sleep_event() which invokes sched_clock_local() and
CPU1 runs a remote wakeup for CPU0 at the same time, which invokes
sched_remote_clock(). The time jump gets propagated to CPU0 via
sched_remote_clock() and stays stale on both cores for ~4 seconds.

There are only two other possibilities, which could cause a stale
sched clock:

1) ktime_get() which reads out CLOCK_MONOTONIC returns a sporadic
   wrong value.

2) sched_clock() which reads the TSC returns a sporadic wrong value.

#1 can be excluded because sched_clock would continue to increase for
   one jiffy and then go stale.

#2 can be excluded because it would not make the clock jump
   forward. It would just result in a stale sched_clock for one jiffy.

After quite some brain twisting and finding the same pattern on other
traces, sched_clock_remote() remained the only place which could cause
such a problem and as explained above it's indeed racy on 32bit
systems.

So while on 64bit systems the readout is atomic, we need to verify the
remote readout on 32bit machines. We need to protect the local->clock
readout in sched_clock_remote() on 32bit as well because an NMI could
hit between the low and the high readout, call sched_clock_local() and
modify local->clock.

Thanks to Siegfried Wulsch for bearing with my debug requests and
going through the tedious tasks of running a bunch of reproducer
systems to generate the debug information which let me decode the
issue.

Reported-by: Siegfried Wulsch <Siegfried.Wulsch@rovema.de>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Link: http://lkml.kernel.org/r/alpine.LFD.2.02.1304051544160.21884@ionos
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agotarget: Fix incorrect fallthrough of ALUA Standby/Offline/Transition CDBs
Nicholas Bellinger [Wed, 10 Apr 2013 22:00:27 +0000 (15:00 -0700)]
target: Fix incorrect fallthrough of ALUA Standby/Offline/Transition CDBs

commit 30f359a6f9da65a66de8cadf959f0f4a0d498bba upstream.

This patch fixes a bug where a handful of informational / control CDBs
that should be allowed during ALUA access state Standby/Offline/Transition
where incorrectly returning CHECK_CONDITION + ASCQ_04H_ALUA_TG_PT_*.

This includes INQUIRY + REPORT_LUNS, which would end up preventing LUN
registration when LUN scanning occured during these ALUA access states.

Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Cc: Hannes Reinecke <hare@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoPM / reboot: call syscore_shutdown() after disable_nonboot_cpus()
Huacai Chen [Sun, 7 Apr 2013 02:14:14 +0000 (02:14 +0000)]
PM / reboot: call syscore_shutdown() after disable_nonboot_cpus()

commit 6f389a8f1dd22a24f3d9afc2812b30d639e94625 upstream.

As commit 40dc166c (PM / Core: Introduce struct syscore_ops for core
subsystems PM) say, syscore_ops operations should be carried with one
CPU on-line and interrupts disabled. However, after commit f96972f2d
(kernel/sys.c: call disable_nonboot_cpus() in kernel_restart()),
syscore_shutdown() is called before disable_nonboot_cpus(), so break
the rules. We have a MIPS machine with a 8259A PIC, and there is an
external timer (HPET) linked at 8259A. Since 8259A has been shutdown
too early (by syscore_shutdown()), disable_nonboot_cpus() runs without
timer interrupt, so it hangs and reboot fails. This patch call
syscore_shutdown() a little later (after disable_nonboot_cpus()) to
avoid reboot failure, this is the same way as poweroff does.

For consistency, add disable_nonboot_cpus() to kernel_halt().

Signed-off-by: Huacai Chen <chenhc@lemote.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agotracing: Fix double free when function profile init failed
Namhyung Kim [Mon, 1 Apr 2013 12:46:23 +0000 (21:46 +0900)]
tracing: Fix double free when function profile init failed

commit 83e03b3fe4daffdebbb42151d5410d730ae50bd1 upstream.

On the failure path, stat->start and stat->pages will refer same page.
So it'll attempt to free the same page again and get kernel panic.

Link: http://lkml.kernel.org/r/1364820385-32027-1-git-send-email-namhyung@kernel.org
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Namhyung Kim <namhyung.kim@lge.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoASoC: wm8903: Fix the bypass to HP/LINEOUT when no DAC or ADC is running
Alban Bedel [Tue, 9 Apr 2013 15:13:59 +0000 (17:13 +0200)]
ASoC: wm8903: Fix the bypass to HP/LINEOUT when no DAC or ADC is running

commit f1ca493b0b5e8f42d3b2dc8877860db2983f47b6 upstream.

The Charge Pump needs the DSP clock to work properly, without it the
bypass to HP/LINEOUT is not working properly. This requirement is not
mentioned in the datasheet but has been confirmed by Mark Brown from
Wolfson.

Signed-off-by: Alban Bedel <alban.bedel@avionic-design.de>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agox86-32, mm: Rip out x86_32 NUMA remapping code
Dave Hansen [Thu, 31 Jan 2013 00:56:16 +0000 (16:56 -0800)]
x86-32, mm: Rip out x86_32 NUMA remapping code

commit f03574f2d5b2d6229dcdf2d322848065f72953c7 upstream.

[was already included in 3.0, but I missed the patch hunk for
 arch/x86/mm/numa_32.c  - gregkh]

This code was an optimization for 32-bit NUMA systems.

It has probably been the cause of a number of subtle bugs over
the years, although the conditions to excite them would have
been hard to trigger.  Essentially, we remap part of the kernel
linear mapping area, and then sometimes part of that area gets
freed back in to the bootmem allocator.  If those pages get
used by kernel data structures (say mem_map[] or a dentry),
there's no big deal.  But, if anyone ever tried to use the
linear mapping for these pages _and_ cared about their physical
address, bad things happen.

For instance, say you passed __GFP_ZERO to the page allocator
and then happened to get handed one of these pages, it zero the
remapped page, but it would make a pte to the _old_ page.
There are probably a hundred other ways that it could screw
with things.

We don't need to hang on to performance optimizations for
these old boxes any more.  All my 32-bit NUMA systems are long
dead and buried, and I probably had access to more than most
people.

This code is causing real things to break today:

https://lkml.org/lkml/2013/1/9/376

I looked in to actually fixing this, but it requires surgery
to way too much brittle code, as well as stuff like
per_cpu_ptr_to_phys().

[ hpa: Cc: this for -stable, since it is a memory corruption issue.
  However, an alternative is to simply mark NUMA as depends BROKEN
  rather than EXPERIMENTAL in the X86_32 subclause... ]

Link: http://lkml.kernel.org/r/20130131005616.1C79F411@kernel.stglabs.ibm.com
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoALSA: usb-audio: fix endianness bug in snd_nativeinstruments_*
Eldad Zack [Fri, 5 Apr 2013 18:49:46 +0000 (20:49 +0200)]
ALSA: usb-audio: fix endianness bug in snd_nativeinstruments_*

commit 889d66848b12d891248b03abcb2a42047f8e172a upstream.

The usb_control_msg() function expects __u16 types and performs
the endianness conversions by itself.
However, in three places, a conversion is performed before it is
handed over to usb_control_msg(), which leads to a double conversion
(= no conversion):
* snd_usb_nativeinstruments_boot_quirk()
* snd_nativeinstruments_control_get()
* snd_nativeinstruments_control_put()

Caught by sparse:

sound/usb/mixer_quirks.c:512:38: warning: incorrect type in argument 6 (different base types)
sound/usb/mixer_quirks.c:512:38:    expected unsigned short [unsigned] [usertype] index
sound/usb/mixer_quirks.c:512:38:    got restricted __le16 [usertype] <noident>
sound/usb/mixer_quirks.c:543:35: warning: incorrect type in argument 5 (different base types)
sound/usb/mixer_quirks.c:543:35:    expected unsigned short [unsigned] [usertype] value
sound/usb/mixer_quirks.c:543:35:    got restricted __le16 [usertype] <noident>
sound/usb/mixer_quirks.c:543:56: warning: incorrect type in argument 6 (different base types)
sound/usb/mixer_quirks.c:543:56:    expected unsigned short [unsigned] [usertype] index
sound/usb/mixer_quirks.c:543:56:    got restricted __le16 [usertype] <noident>
sound/usb/quirks.c:502:35: warning: incorrect type in argument 5 (different base types)
sound/usb/quirks.c:502:35:    expected unsigned short [unsigned] [usertype] value
sound/usb/quirks.c:502:35:    got restricted __le16 [usertype] <noident>

Signed-off-by: Eldad Zack <eldad@fogrefinery.com>
Acked-by: Daniel Mack <zonque@gmail.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agobfa: fix for Brocade FC Direct Attach LUN discovery failure
Hannes Reinecke [Sat, 13 Apr 2013 14:37:26 +0000 (16:37 +0200)]
bfa: fix for Brocade FC Direct Attach LUN discovery failure
(bnc#816037).

suse-commit: 6484a0fe9469a0e0bd84c1d67d1373a4a6409057

4 years agobfa: fix faulty handling of states in lps state machine
Hannes Reinecke [Sat, 13 Apr 2013 14:37:26 +0000 (16:37 +0200)]
bfa: fix faulty handling of states in lps state machine
(bnc#816022).

suse-commit: 55f71527b89901e23775ef2f1eff98ed5016b2f4

4 years agocciss: kdump fails on SmartArray P410i (bnc#812740).
Hannes Reinecke [Sat, 13 Apr 2013 14:24:01 +0000 (16:24 +0200)]
cciss: kdump fails on SmartArray P410i (bnc#812740).

suse-commit: c19b9809465ab8bc3590820a3a480c9115216a3c

4 years agoMerge branch 'SLE11-SP3' of ssh://kerncvs.suse.de/home/git/kernel-source into SLE11-SP3
Michal Srb [Fri, 19 Apr 2013 14:03:26 +0000 (16:03 +0200)]
Merge branch 'SLE11-SP3' of ssh://kerncvs.suse.de/home/git/kernel-source into SLE11-SP3

suse-commit: d0cd647f5af1376312626beaffd9932bc5baed8d

4 years agoFix DRM mismerges.
Michal Srb [Fri, 19 Apr 2013 14:02:02 +0000 (16:02 +0200)]
Fix DRM mismerges.

- Refresh patches.drm/1822-drm-i915-kick-any-firmware-framebuffers-before-claiming-the-gtt.
- Refresh patches.drm/1874-drm-i915-agp-intel-gtt-prep-work-for-direct-setup.
- Refresh patches.drm/2271-merge-tag-v3-6-rc2-into-drm-intel-next.
- Refresh patches.drm/2328-drm-i915-add-workarounds-directly-to-gen6_render_ring_flush.
- Refresh patches.drm/3029-drm-i915-stop-using-agp-layer-for-gen6.

suse-commit: aa02d6b2868013baf608c3fd7a5812ac1999c69f

4 years agoqla4xxx: v5.03.00.05.11.3-k0 (FATE#313902 bnc#815913).
Lee Duncan [Fri, 19 Apr 2013 13:59:39 +0000 (06:59 -0700)]
qla4xxx: v5.03.00.05.11.3-k0 (FATE#313902 bnc#815913).

suse-commit: 659ba5e92163b7f059a7d49612099c7bee7bbc07

4 years agoqla4xxx: Assign values using correct datatype (FATE#313902
Lee Duncan [Fri, 19 Apr 2013 13:59:39 +0000 (06:59 -0700)]
qla4xxx: Assign values using correct datatype (FATE#313902
bnc#815913).

suse-commit: c54e086b122bb4fd3eecc6c01a066ad4e984276c

4 years agoqla4xxx: Fix smatch warnings (FATE#313902 bnc#815913).
Lee Duncan [Fri, 19 Apr 2013 13:59:39 +0000 (06:59 -0700)]
qla4xxx: Fix smatch warnings (FATE#313902 bnc#815913).

suse-commit: c0dda60f69eef562097b25952e66faa74020b9d9

4 years agoqla4xxx: Fix sparse warning for qla4xxx_sysfs_ddb_tgt_create
Lee Duncan [Fri, 19 Apr 2013 13:59:39 +0000 (06:59 -0700)]
qla4xxx: Fix sparse warning for qla4xxx_sysfs_ddb_tgt_create
(FATE#313902 bnc#815913).

suse-commit: 52a022687e9b1a50c0aaa9f783a8c1173a6bf192

4 years agoqla4xxx: Silence gcc warning (FATE#313902 bnc#815913).
Lee Duncan [Fri, 19 Apr 2013 13:59:39 +0000 (06:59 -0700)]
qla4xxx: Silence gcc warning (FATE#313902 bnc#815913).

suse-commit: c5972346419c24463a906aab5f4bafd73a7abedf

4 years agoipr: Need to reset adapter after the 6th EEH error (bnc#816120).
Torsten Duwe [Fri, 19 Apr 2013 12:09:12 +0000 (14:09 +0200)]
ipr: Need to reset adapter after the 6th EEH error (bnc#816120).

suse-commit: 4ea7c1acd7ce13043c63f7112cd5144e779567da

4 years agoipr: SATA DVD probing failed with 64bit adapter (bnc#816118).
Torsten Duwe [Fri, 19 Apr 2013 12:09:12 +0000 (14:09 +0200)]
ipr: SATA DVD probing failed with 64bit adapter (bnc#816118).

suse-commit: a944bc2e724c3d5bbd6d7ad3d35b9f90b3ca1b96

4 years agozcrypt: ap bus rescan problem when toggle crypto adapters on/off
John Jolly [Thu, 18 Apr 2013 23:46:59 +0000 (01:46 +0200)]
zcrypt: ap bus rescan problem when toggle crypto adapters on/off
(bnc#815926, LTC#91798).

suse-commit: 561472ede8477865bbb848e503a96adcf68562a5

4 years ago- patches.fixes/mm-make-snapshotting-pages-for-stable-writes-a-per-bio-operation...
Mel Gorman [Fri, 12 Apr 2013 16:51:29 +0000 (17:51 +0100)]
- patches.fixes/mm-make-snapshotting-pages-for-stable-writes-a-per-bio-operation.patch:
  mm: Make snapshotting pages for stable writes a per-bio operation
- patches.suse/fs-knows-MAY_APPEND.diff
  Refresh
  Only enable stable page writes when necessary (bnc#807517).

suse-commit: e6e0d84dcd192d54f878b40b28e0958960d4b763

4 years agoLinux 3.0.73
Greg Kroah-Hartman [Fri, 12 Apr 2013 16:18:32 +0000 (09:18 -0700)]
Linux 3.0.73

4 years agort2x00: rt2x00pci_regbusy_read() - only print register access failure once
Tim Gardner [Mon, 18 Feb 2013 19:56:28 +0000 (12:56 -0700)]
rt2x00: rt2x00pci_regbusy_read() - only print register access failure once

commit 83589b30f1e1dc9898986293c9336b8ce1705dec upstream.

BugLink: http://bugs.launchpad.net/bugs/1128840
It appears that when this register read fails it never recovers, so
I think there is no need to repeat the same error message ad infinitum.

Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Cc: users@rt2x00.serialmonkey.com
Cc: netdev@vger.kernel.org
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoRevert "mwifiex: cancel cmd timer and free curr_cmd in shutdown process
Greg Kroah-Hartman [Wed, 10 Apr 2013 22:21:39 +0000 (15:21 -0700)]
Revert "mwifiex: cancel cmd timer and free curr_cmd in shutdown process

revert commit b9f1f48ce20a1b923429c216669d03b5a900a8cf which is commit
084c7189acb3f969c855536166042e27f5dd703f upstream.

It shouldn't have been applied to the 3.0-stable tree.

Reported-by: Ben Hutchings <ben@decadent.org.uk>
Cc: Marco Cesarano <marco@marvell.com>
Reported-by: Bing Zhao <bzhao@marvell.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agox86-32, mm: Rip out x86_32 NUMA remapping code
Dave Hansen [Thu, 31 Jan 2013 00:56:16 +0000 (16:56 -0800)]
x86-32, mm: Rip out x86_32 NUMA remapping code

commit f03574f2d5b2d6229dcdf2d322848065f72953c7 upstream.

This code was an optimization for 32-bit NUMA systems.

It has probably been the cause of a number of subtle bugs over
the years, although the conditions to excite them would have
been hard to trigger.  Essentially, we remap part of the kernel
linear mapping area, and then sometimes part of that area gets
freed back in to the bootmem allocator.  If those pages get
used by kernel data structures (say mem_map[] or a dentry),
there's no big deal.  But, if anyone ever tried to use the
linear mapping for these pages _and_ cared about their physical
address, bad things happen.

For instance, say you passed __GFP_ZERO to the page allocator
and then happened to get handed one of these pages, it zero the
remapped page, but it would make a pte to the _old_ page.
There are probably a hundred other ways that it could screw
with things.

We don't need to hang on to performance optimizations for
these old boxes any more.  All my 32-bit NUMA systems are long
dead and buried, and I probably had access to more than most
people.

This code is causing real things to break today:

https://lkml.org/lkml/2013/1/9/376

I looked in to actually fixing this, but it requires surgery
to way too much brittle code, as well as stuff like
per_cpu_ptr_to_phys().

[ hpa: Cc: this for -stable, since it is a memory corruption issue.
  However, an alternative is to simply mark NUMA as depends BROKEN
  rather than EXPERIMENTAL in the X86_32 subclause... ]

Link: http://lkml.kernel.org/r/20130131005616.1C79F411@kernel.stglabs.ibm.com
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Cc: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agomm: prevent mmap_cache race in find_vma()
Jan Stancek [Mon, 8 Apr 2013 20:00:02 +0000 (13:00 -0700)]
mm: prevent mmap_cache race in find_vma()

commit b6a9b7f6b1f21735a7456d534dc0e68e61359d2c upstream.

find_vma() can be called by multiple threads with read lock
held on mm->mmap_sem and any of them can update mm->mmap_cache.
Prevent compiler from re-fetching mm->mmap_cache, because other
readers could update it in the meantime:

               thread 1                             thread 2
                                        |
  find_vma()                            |  find_vma()
    struct vm_area_struct *vma = NULL;  |
    vma = mm->mmap_cache;               |
    if (!(vma && vma->vm_end > addr     |
        && vma->vm_start <= addr)) {    |
                                        |    mm->mmap_cache = vma;
    return vma;                         |
     ^^ compiler may optimize this      |
        local variable out and re-read  |
        mm->mmap_cache                  |

This issue can be reproduced with gcc-4.8.0-1 on s390x by running
mallocstress testcase from LTP, which triggers:

  kernel BUG at mm/rmap.c:1088!
    Call Trace:
     ([<000003d100c57000>] 0x3d100c57000)
      [<000000000023a1c0>] do_wp_page+0x2fc/0xa88
      [<000000000023baae>] handle_pte_fault+0x41a/0xac8
      [<000000000023d832>] handle_mm_fault+0x17a/0x268
      [<000000000060507a>] do_protection_exception+0x1e2/0x394
      [<0000000000603a04>] pgm_check_handler+0x138/0x13c
      [<000003fffcf1f07a>] 0x3fffcf1f07a
    Last Breaking-Event-Address:
      [<000000000024755e>] page_add_new_anon_rmap+0xc2/0x168

Thanks to Jakub Jelinek for his insight on gcc and helping to
track this down.

Signed-off-by: Jan Stancek <jstancek@redhat.com>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Hugh Dickins <hughd@google.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[bwh: Backported to 3.2: adjust context, indentation]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agothermal: return an error on failure to register thermal class
Richard Guy Briggs [Tue, 12 Feb 2013 19:39:44 +0000 (19:39 +0000)]
thermal: return an error on failure to register thermal class

commit da28d966f6aa942ae836d09729f76a1647932309 upstream.

The return code from the registration of the thermal class is used to
unallocate resources, but this failure isn't passed back to the caller of
thermal_init.  Return this failure back to the caller.

This bug was introduced in changeset 4cb18728 which overwrote the return code
when the variable was re-used to catch the return code of the registration of
the genetlink thermal socket family.

Signed-off-by: Richard Guy Briggs <rbriggs@redhat.com>
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
Cc: Jonghwan Choi <jhbird.choi@samsung.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoblock: avoid using uninitialized value in from queue_var_store
Arnd Bergmann [Wed, 3 Apr 2013 19:53:57 +0000 (21:53 +0200)]
block: avoid using uninitialized value in from queue_var_store

commit c678ef5286ddb5cf70384ad5af286b0afc9b73e1 upstream.

As found by gcc-4.8, the QUEUE_SYSFS_BIT_FNS macro creates functions
that use a value generated by queue_var_store independent of whether
that value was set or not.

block/blk-sysfs.c: In function 'queue_store_nonrot':
block/blk-sysfs.c:244:385: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]

Unlike most other such warnings, this one is not a false positive,
writing any non-number string into the sysfs files indeed has
an undefined result, rather than returning an error.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agocrypto: gcm - fix assumption that assoc has one segment
Jussi Kivilinna [Thu, 28 Mar 2013 19:54:03 +0000 (21:54 +0200)]
crypto: gcm - fix assumption that assoc has one segment

commit d3dde52209ab571e4e2ec26c66f85ad1355f7475 upstream.

rfc4543(gcm(*)) code for GMAC assumes that assoc scatterlist always contains
only one segment and only makes use of this first segment. However ipsec passes
assoc with three segments when using 'extended sequence number' thus in this
case rfc4543(gcm(*)) fails to function correctly. Patch fixes this issue.

Reported-by: Chaoxing Lin <Chaoxing.Lin@ultra-3eti.com>
Tested-by: Chaoxing Lin <Chaoxing.Lin@ultra-3eti.com>
Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agospinlocks and preemption points need to be at least compiler barriers
Linus Torvalds [Tue, 9 Apr 2013 17:48:33 +0000 (10:48 -0700)]
spinlocks and preemption points need to be at least compiler barriers

commit 386afc91144b36b42117b0092893f15bc8798a80 upstream.

In UP and non-preempt respectively, the spinlocks and preemption
disable/enable points are stubbed out entirely, because there is no
regular code that can ever hit the kind of concurrency they are meant to
protect against.

However, while there is no regular code that can cause scheduling, we
_do_ end up having some exceptional (literally!) code that can do so,
and that we need to make sure does not ever get moved into the critical
region by the compiler.

In particular, get_user() and put_user() is generally implemented as
inline asm statements (even if the inline asm may then make a call
instruction to call out-of-line), and can obviously cause a page fault
and IO as a result.  If that inline asm has been scheduled into the
middle of a preemption-safe (or spinlock-protected) code region, we
obviously lose.

Now, admittedly this is *very* unlikely to actually ever happen, and
we've not seen examples of actual bugs related to this.  But partly
exactly because it's so hard to trigger and the resulting bug is so
subtle, we should be extra careful to get this right.

So make sure that even when preemption is disabled, and we don't have to
generate any actual *code* to explicitly tell the system that we are in
a preemption-disabled region, we need to at least tell the compiler not
to move things around the critical region.

This patch grew out of the same discussion that caused commits
79e5f05edcbf ("ARC: Add implicit compiler barrier to raw_local_irq*
functions") and 3e2e0d2c222b ("tile: comment assumption about
__insn_mtspr for <asm/irqflags.h>") to come about.

Note for stable: use discretion when/if applying this.  As mentioned,
this bug may never have actually bitten anybody, and gcc may never have
done the required code motion for it to possibly ever trigger in
practice.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <srostedt@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agopowerpc: pSeries_lpar_hpte_remove fails from Adjunct partition being performed before...
Michael Wolf [Fri, 5 Apr 2013 10:41:40 +0000 (10:41 +0000)]
powerpc: pSeries_lpar_hpte_remove fails from Adjunct partition being performed before the ANDCOND test

commit 9fb2640159f9d4f5a2a9d60e490482d4cbecafdb upstream.

Some versions of pHyp will perform the adjunct partition test before the
ANDCOND test.  The result of this is that H_RESOURCE can be returned and
cause the BUG_ON condition to occur. The HPTE is not removed.  So add a
check for H_RESOURCE, it is ok if this HPTE is not removed as
pSeries_lpar_hpte_remove is looking for an HPTE to remove and not a
specific HPTE to remove.  So it is ok to just move on to the next slot
and try again.

Signed-off-by: Michael Wolf <mjw@linux.vnet.ibm.com>
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoftrace: Consistently restore trace function on sysctl enabling
Jan Kiszka [Tue, 26 Mar 2013 16:53:03 +0000 (17:53 +0100)]
ftrace: Consistently restore trace function on sysctl enabling

commit 5000c418840b309251c5887f0b56503aae30f84c upstream.

If we reenable ftrace via syctl, we currently set ftrace_trace_function
based on the previous simplistic algorithm. This is inconsistent with
what update_ftrace_function does. So better call that helper instead.

Link: http://lkml.kernel.org/r/5151D26F.1070702@siemens.com
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoalpha: Add irongate_io to PCI bus resources
Jay Estabrook [Sun, 7 Apr 2013 09:36:09 +0000 (21:36 +1200)]
alpha: Add irongate_io to PCI bus resources

commit aa8b4be3ac049c8b1df2a87e4d1d902ccfc1f7a9 upstream.

Fixes a NULL pointer dereference at boot on UP1500.

Reviewed-and-Tested-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Jay Estabrook <jay.estabrook@gmail.com>
Signed-off-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Michael Cree <mcree@orcon.net.nz>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agolibata: Set max sector to 65535 for Slimtype DVD A DS8A8SH drive
Shan Hai [Mon, 18 Mar 2013 02:30:44 +0000 (10:30 +0800)]
libata: Set max sector to 65535 for Slimtype DVD A DS8A8SH drive

commit a32450e127fc6e5ca6d958ceb3cfea4d30a00846 upstream.

The Slimtype DVD A  DS8A8SH drive locks up when max sector is smaller than
65535, and the blow backtrace is observed on locking up:

INFO: task flush-8:32:1130 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
flush-8:32      D ffffffff8180cf60     0  1130      2 0x00000000
 ffff880273aef618 0000000000000046 0000000000000005 ffff880273aee000
 ffff880273aee000 ffff880273aeffd8 ffff880273aee010 ffff880273aee000
 ffff880273aeffd8 ffff880273aee000 ffff88026e842ea0 ffff880274a10000
Call Trace:
 [<ffffffff8168fc2d>] schedule+0x5d/0x70
 [<ffffffff8168fccc>] io_schedule+0x8c/0xd0
 [<ffffffff81324461>] get_request+0x731/0x7d0
 [<ffffffff8133dc60>] ? cfq_allow_merge+0x50/0x90
 [<ffffffff81083aa0>] ? wake_up_bit+0x40/0x40
 [<ffffffff81320443>] ? bio_attempt_back_merge+0x33/0x110
 [<ffffffff813248ea>] blk_queue_bio+0x23a/0x3f0
 [<ffffffff81322176>] generic_make_request+0xc6/0x120
 [<ffffffff81322308>] submit_bio+0x138/0x160
 [<ffffffff811d7596>] ? bio_alloc_bioset+0x96/0x120
 [<ffffffff811d1f61>] submit_bh+0x1f1/0x220
 [<ffffffff811d48b8>] __block_write_full_page+0x228/0x340
 [<ffffffff811d3650>] ? attach_nobh_buffers+0xc0/0xc0
 [<ffffffff811d8960>] ? I_BDEV+0x10/0x10
 [<ffffffff811d8960>] ? I_BDEV+0x10/0x10
 [<ffffffff811d4ab6>] block_write_full_page_endio+0xe6/0x100
 [<ffffffff811d4ae5>] block_write_full_page+0x15/0x20
 [<ffffffff811d9268>] blkdev_writepage+0x18/0x20
 [<ffffffff81142527>] __writepage+0x17/0x40
 [<ffffffff811438ba>] write_cache_pages+0x34a/0x4a0
 [<ffffffff81142510>] ? set_page_dirty+0x70/0x70
 [<ffffffff81143a61>] generic_writepages+0x51/0x80
 [<ffffffff81143ab0>] do_writepages+0x20/0x50
 [<ffffffff811c9ed6>] __writeback_single_inode+0xa6/0x2b0
 [<ffffffff811ca861>] writeback_sb_inodes+0x311/0x4d0
 [<ffffffff811caaa6>] __writeback_inodes_wb+0x86/0xd0
 [<ffffffff811cad43>] wb_writeback+0x1a3/0x330
 [<ffffffff816916cf>] ? _raw_spin_lock_irqsave+0x3f/0x50
 [<ffffffff811b8362>] ? get_nr_inodes+0x52/0x70
 [<ffffffff811cb0ac>] wb_do_writeback+0x1dc/0x260
 [<ffffffff8168dd34>] ? schedule_timeout+0x204/0x240
 [<ffffffff811cb232>] bdi_writeback_thread+0x102/0x2b0
 [<ffffffff811cb130>] ? wb_do_writeback+0x260/0x260
 [<ffffffff81083550>] kthread+0xc0/0xd0
 [<ffffffff81083490>] ? kthread_worker_fn+0x1b0/0x1b0
 [<ffffffff8169a3ec>] ret_from_fork+0x7c/0xb0
 [<ffffffff81083490>] ? kthread_worker_fn+0x1b0/0x1b0

 The above trace was triggered by
   "dd if=/dev/zero of=/dev/sr0 bs=2048 count=32768"

 It was previously working by accident, since another bug introduced
 by 4dce8ba94c7 (libata: Use 'bool' return value for ata_id_XXX) caused
 all drives to use maxsect=65535.

Signed-off-by: Shan Hai <shan.hai@windriver.com>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agolibata: Use integer return value for atapi_command_packet_set
Shan Hai [Mon, 18 Mar 2013 02:30:43 +0000 (10:30 +0800)]
libata: Use integer return value for atapi_command_packet_set

commit d8668fcb0b257d9fdcfbe5c172a99b8d85e1cd82 upstream.

The function returns type of ATAPI drives so it should return integer value.
The commit 4dce8ba94c7 (libata: Use 'bool' return value for ata_id_XXX) since
v2.6.39 changed the type of return value from int to bool, the change would
cause all of the ATAPI class drives to be treated as TYPE_TAPE and the
max_sectors of the drives to be set to 65535 because of the commit
f8d8e5799b7(libata: increase 128 KB / cmd limit for ATAPI tape drives), for the
function would return true for all ATAPI class drives and the TYPE_TAPE is
defined as 0x01.

Signed-off-by: Shan Hai <shan.hai@windriver.com>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoext4: fixup 64-bit divides in 3.0-stable backport of upstream fix
Todd Poynor [Fri, 5 Apr 2013 23:38:53 +0000 (16:38 -0700)]
ext4: fixup 64-bit divides in 3.0-stable backport of upstream fix

Replace C division operators with div64_u64 for divides introduced in:
commit 503f4bdcc078e7abee273a85ce322de81b18a224
ext4: use atomic64_t for the per-flexbg free_clusters count

Specific to the 3.0-stable backport of the upstream patch.

Signed-off-by: Todd Poynor <toddpoynor@google.com>
Reviewed-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Cc: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoALSA: hda - fix typo in proc output
David Henningsson [Thu, 4 Apr 2013 09:47:13 +0000 (11:47 +0200)]
ALSA: hda - fix typo in proc output

commit aeb3a97222832e5457c4b72d72235098ce4bfe8d upstream.

Rename "Digitial In" to "Digital In". This function is only used for
proc output, so should not cause any problems to change.

Signed-off-by: David Henningsson <david.henningsson@canonical.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoALSA: hda - bug fix on return value when getting HDMI ELD info
Mengdong Lin [Thu, 28 Mar 2013 09:20:22 +0000 (05:20 -0400)]
ALSA: hda - bug fix on return value when getting HDMI ELD info

commit 2ef5692efad330b67a234e2c49edad38538751e7 upstream.

In function snd_hdmi_get_eld(), the variable 'ret' should be initialized to 0.
Otherwise it will be returned uninitialized as non-zero after ELD info is got
successfully. Thus hdmi_present_sense() will always assume ELD info is invalid
by mistake, and /proc file system cannot show the proper ELD info.

Signed-off-by: Mengdong Lin <mengdong.lin@intel.com>
Acked-by: David Henningsson <david.henningsson@canonical.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoreiserfs: Fix warning and inode leak when deleting inode with xattrs
Jan Kara [Fri, 29 Mar 2013 14:39:16 +0000 (15:39 +0100)]
reiserfs: Fix warning and inode leak when deleting inode with xattrs

commit 35e5cbc0af240778e61113286c019837e06aeec6 upstream.

After commit 21d8a15a (lookup_one_len: don't accept . and ..) reiserfs
started failing to delete xattrs from inode. This was due to a buggy
test for '.' and '..' in fill_with_dentries() which resulted in passing
'.' and '..' entries to lookup_one_len() in some cases. That returned
error and so we failed to iterate over all xattrs of and inode.

Fix the test in fill_with_dentries() along the lines of the one in
lookup_one_len().

Reported-by: Pawel Zawora <pzawora@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoUBIFS: make space fixup work in the remount case
Artem Bityutskiy [Thu, 14 Mar 2013 08:49:23 +0000 (10:49 +0200)]
UBIFS: make space fixup work in the remount case

commit 67e753ca41782913d805ff4a8a2b0f60b26b7915 upstream.

The UBIFS space fixup is a useful feature which allows to fixup the "broken"
flash space at the time of the first mount. The "broken" space is usually the
result of using a "dumb" industrial flasher which is not able to skip empty
NAND pages and just writes all 0xFFs to the empty space, which has grave
side-effects for UBIFS when UBIFS trise to write useful data to those empty
pages.

The fix-up feature works roughly like this:
1. mkfs.ubifs sets the fixup flag in UBIFS superblock when creating the image
   (see -F option)
2. when the file-system is mounted for the first time, UBIFS notices the fixup
   flag and re-writes the entire media atomically, which may take really a lot
   of time.
3. UBIFS clears the fixup flag in the superblock.

This works fine when the file system is mounted R/W for the very first time.
But it did not really work in the case when we first mount the file-system R/O,
and then re-mount R/W. The reason was that we started the fixup procedure too
late, which we cannot really do because we have to fixup the space before it
starts being used.

Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Reported-by: Mark Jackson <mpfj-list@mimc.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoASoC: dma-sh7760: Fix compile error
Lars-Peter Clausen [Fri, 15 Mar 2013 10:26:15 +0000 (11:26 +0100)]
ASoC: dma-sh7760: Fix compile error

commit 417a1178f1bf3cdc606376b3ded3a22489fbb3eb upstream.

The dma-sh7760 currently fails with the following compile error:
sound/soc/sh/dma-sh7760.c:346:2: error: unknown field 'pcm_ops' specified in initializer
sound/soc/sh/dma-sh7760.c:346:2: warning: initialization from incompatible pointer type
sound/soc/sh/dma-sh7760.c:347:2: error: unknown field 'pcm_new' specified in initializer
sound/soc/sh/dma-sh7760.c:347:2: warning: initialization makes integer from pointer without a cast
sound/soc/sh/dma-sh7760.c:348:2: error: unknown field 'pcm_free' specified in initializer
sound/soc/sh/dma-sh7760.c:348:2: warning: initialization from incompatible pointer type
sound/soc/sh/dma-sh7760.c: In function 'sh7760_soc_platform_probe':
sound/soc/sh/dma-sh7760.c:353:2: warning: passing argument 2 of 'snd_soc_register_platform' from incompatible pointer type
include/sound/soc.h:368:5: note: expected 'struct snd_soc_platform_driver *' but argument is of type 'struct snd_soc_platform *'

This is due the misnaming of the snd_soc_platform_driver type name and 'ops'
field. The issue was introduced in commit f0fba2a("ASoC: multi-component - ASoC
Multi-Component Support").

Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4 years agoFix race between starved list processing and device removal
Hannes Reinecke [Thu, 11 Apr 2013 16:56:13 +0000 (18:56 +0200)]
Fix race between starved list processing and device removal
(bnc#812224).

suse-commit: b513bfec38c2c9161ecb8600fe808edde7c87ca3

4 years agokeep tick_do_timer_cpu on CPU0 with nohz off (bnc#727639).
Jiri Bohac [Thu, 18 Apr 2013 15:38:25 +0000 (17:38 +0200)]
keep tick_do_timer_cpu on CPU0 with nohz off (bnc#727639).

suse-commit: 0f67f1db053f4bffcef84a61a0fdf3cc0de29215

4 years agoDRM/mgag200: Add bandwidth and resolution limits (bnc #806990).
Egbert Eich [Thu, 18 Apr 2013 15:10:38 +0000 (17:10 +0200)]
DRM/mgag200: Add bandwidth and resolution limits (bnc #806990).

suse-commit: 920b4768a4c0c7ee2726d046c2fbb49bdb5e782f

4 years agoigb: fix PHC stopping on max freq (bnc#814604).
Jiri Bohac [Thu, 18 Apr 2013 14:33:54 +0000 (16:33 +0200)]
igb: fix PHC stopping on max freq (bnc#814604).

suse-commit: 474daac52ff3499614cbb442986a3d10a0a73390

4 years agobnx2x: Prevent null pointer dereference in AFEX mode
Benjamin Poirier [Thu, 18 Apr 2013 14:17:44 +0000 (10:17 -0400)]
bnx2x: Prevent null pointer dereference in AFEX mode
(bnc#815661).

suse-commit: abcd72960d1daee7510e82bc4bdc01b437a68c43

4 years agobnx2x: Fix KR2 rapid link flap (bnc#815178).
Benjamin Poirier [Thu, 18 Apr 2013 14:17:44 +0000 (10:17 -0400)]
bnx2x: Fix KR2 rapid link flap (bnc#815178).

suse-commit: f2d83addc6bb078bae5c760fc77e7a37f633da62