linux-next: back merge of Linus' tree into the vfio tree

Hi Alex, I noticed that you have back merged Linus' tree into yours. Linus usually takes a dim view of that - especially when there is no explanation in the merge commit message. i.e. you shouldn't to that unless you really need to - and then you should explain why you did it. -- Cheers,

Re: [PATCH 0/8] ceph: fscache support & upstream changes

On Thu, 5 Sep 2013, Milosz Tanski wrote: > Hey gang I think this should be final revision of these changes. The changes > are: > > * David rewrote the cookie validity check (that originally was written by >Hongyi Jia). You might have seen some emails flying about doing it the >right

Re: [git pull] drm tree for 3.12-rc1

On Thu, Sep 5, 2013 at 3:51 PM, Linus Torvalds wrote: > > Looking more closely at the log-file, I notice that the oops, pressed the send-button a bit too early.. Anyway, looking more closely at the log-file, I notice that while it has zero errors, it does seem to end just where a successful

[PATCH 1/9] x86/UV: Move NMI support

This patch moves the UV NMI support from the x2apic file to a new separate uv_nmi.c file in preparation for the next sequence of patches. It prevents upcoming bloat of the x2apic file, and has the added benefit of putting the upcoming /sys/module parameters under the name 'uv_nmi' instead of

[PATCH 2/9] x86/UV: Update UV support for external NMI signals

The current UV NMI handler has not been updated for the changes in the system NMI handler and the perf operations. The UV NMI handler reads an MMR in the UV Hub to check to see if the NMI event was caused by the external 'system NMI' that the operator can initiate on the System Mgmt Controller.

Re: [ 00/14] 3.4.61-stable review

On Thu, Sep 05, 2013 at 01:28:11PM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.4.61 release. > There are 14 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me

Re: [PATCH 3/3] irq: Comment on the use of inline stack for ksoftirq

On Thu, Sep 05, 2013 at 05:33:24PM +0200, Frederic Weisbecker wrote: > Ksoftirqd shouldn't need softirq stack since it's executing > in a kernel thread with a callstack that is only beginning at > this stage. > > Lets comment about that for clarity. > > Signed-off-by: Frederic Weisbecker > Cc:

[PATCH 6/9] x86/UV: Add call to KGDB/KDB from NMI handler

This patch restores the capability to enter KDB (and KGDB) from the UV NMI handler. This is needed because the UV system console is not capable of sending the 'break' signal to the serial console port. It is also useful when the kernel is hung in such a way that it isn't responding to normal

Re: linux-next: back merge of Linus' tree into the vfio tree

On Fri, 2013-09-06 at 09:08 +1000, Stephen Rothwell wrote: > Hi Alex, > > I noticed that you have back merged Linus' tree into yours. Linus > usually takes a dim view of that - especially when there is no > explanation in the merge commit message. i.e. you shouldn't to that > unless you really

[PATCH 9/9] x86/UV: Add ability to disable UV NMI handler

For performance reasons, the NMI handler may be disabled to lessen the performance impact caused by the multiple perf tools running concurently. If the system nmi command is issued when the UV NMI handler is disabled, the "Dazed and Confused" messages occur for all cpus. The NMI handler is

[PATCH 4/9] x86/UV: Add kdump to UV NMI handler

If a system has hung and it no longer responds to external events, this patch adds the capability of doing a standard kdump and system reboot then triggered by the system NMI command. It is enabled when the nmi action is changed to "kdump" and the kernel is built with CONFIG_KEXEC enabled.

Re: [ 0/7] 3.0.95-stable review

On Thu, Sep 05, 2013 at 01:28:33PM -0700, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.0.95 release. > There are 7 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know.

[PATCH 7/9] KGDB/KDB: add new system NMI entry code to KDB

This patch adds a new "KDB_REASON" code (KDB_REASON_SYSTEM_NMI). This is purely cosmetic to distinguish it from the other various reasons that NMI may occur and are usually after an error occurred. Also the dumping of registers is not done to more closely match what is displayed when KDB is

[PATCH 5/9] KGDB/KDB: add support for external NMI handler to call KGDB/KDB.

This patch adds a kgdb_nmicallin() interface that can be used by external NMI handlers to call the KGDB/KDB handler. The primary need for this is for those types of NMI interrupts where all the CPUs have already received the NMI signal. Therefore no send_IPI(NMI) is required, and in fact it will

Re: [git pull] drm tree for 3.12-rc1

On Thu, Sep 5, 2013 at 3:51 PM, Linus Torvalds wrote: > > I've booted a few times since (it's the merge window, so I boot fairly > frequently), and it hasn't happened again... .. and of course, after I say that, on the very next boot it then happened three times in a row until it magically

[PATCH 8/9] x86/UV: Add uvtrace support

This patch adds support for the uvtrace module by providing a skeleton call to the registered trace function. It also provides another separate 'NMI' tracer that is triggered by the system wide 'power nmi' command. Signed-off-by: Mike Travis Reviewed-by: Dimitri Sivanich Reviewed-by: Hedi

[PATCH 3/9] x86/UV: Add summary of cpu activity to UV NMI handler

The standard NMI handler dumps the states of all the cpus. This includes a full register dump and stack trace. This can be way more information than what is needed. This patch adds a "summary" dump that is basically a form of the "ps" command. It includes the symbolic IP address as well as the

Re: [PATCH] vfio: fix documentation

On Thu, 2013-09-05 at 15:22 -0700, Zi Shen Lim wrote: > Signed-off-by: Zi Shen Lim > --- Applied. Thanks! Alex > Documentation/vfio.txt | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt > index d7993dc..b9ca023

Re: [GIT] Sparc

Hello. On 09/06/2013 12:44 AM, David Miller wrote: Several bug fixes (from Kirill Tkhai, Geery Uytterhoeven, and Alexey Dobriyan) and some support for Fujitsu sparc64x chips (from Allen Pais). Please pull, thanks a lot! You meant that for 'linux-sparc', not 'linux-ide', right? :-)

Re: [git pull] drm tree for 3.12-rc1

On Thu, 5 Sep 2013 12:18:32 -0700 Linus Torvalds wrote: > On Thu, Sep 5, 2013 at 3:41 AM, Dave Airlie wrote: > > > > i915: Haswell PC8+ support and eLLC support, HDMI 4K support, initial > > per-process VMA pieces, > > watermark reworks, convert to generic hdmi infoframes, encoder > >

Re: Excess dmesg output from ACPIPHP on boot (was: Re: [PATCH 25/30] ACPI / hotplug / PCI: Check for new devices on enabled slots)

On Thursday, September 05, 2013 04:17:25 PM Alex Williamson wrote: > On Thu, 2013-09-05 at 23:39 +0200, Rafael J. Wysocki wrote: > > On Thursday, September 05, 2013 09:44:26 PM Rafael J. Wysocki wrote: > > > On Thursday, September 05, 2013 08:21:41 AM Alex Williamson wrote: > > > > [...] > > > >

Re: [RFC PATCH] mmc: Enable wakeup_sources for mmc core

Hi Ulf, Thanks for reviewing this, it was very helpful! > 1. mmc_detect_change does obviously not have to be run the same number > of times as the mmc_rescan function. In other words, the calls to > __pm_stay_awake is not paired with __pm_relay, I suppose this does not > matter? It shouldn't,

Re: kobject: delayed kobject release: help find buggy drivers

On Thu, Sep 05, 2013 at 05:26:06PM -0400, Dave Jones wrote: > On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote: > > > Trying without serial console next.. > > > > rebuilt with all serial turned off. > > > > no luck, then it oopses somewhere else. I'm suspecting something isn't >

[PATCH 7/8] ceph: page still marked private_2

Previous patch that allowed us to cleanup most of the issues with pages marked as private_2 when calling ceph_readpages. However, there seams to be a case in the error case clean up in start read that still trigers this from time to time. I've only seen this one a couple times. BUG: Bad page

[PATCH 8/8] ceph: Do not do invalidate if the filesystem is mounted nofsc

Previously we would always try to enqueue work even if the filesystem is not mounted with fscache enabled (or the file has no cookie). In the case of the filesystem mouned nofsc (but with fscache compiled in) this would lead to a crash. Signed-off-by: Milosz Tanski --- fs/ceph/cache.c |4

[PATCH 4/8] ceph: use fscache as a local presisent cache

Adding support for fscache to the Ceph filesystem. This would bring it to on par with some of the other network filesystems in Linux (like NFS, AFS, etc...) In order to mount the filesystem with fscache the 'fsc' mount option must be passed. Signed-off-by: Milosz Tanski Signed-off-by: Sage Weil

[PATCH] vfio: fix documentation

Signed-off-by: Zi Shen Lim --- Documentation/vfio.txt | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/vfio.txt b/Documentation/vfio.txt index d7993dc..b9ca023 100644 --- a/Documentation/vfio.txt +++ b/Documentation/vfio.txt @@ -167,8 +167,8 @@ group and

[PATCH 5/8] ceph: clean PgPrivate2 on returning from readpages

In some cases the ceph readapages code code bails without filling all the pages already marked by fscache. When we return back to readahead code this causes a BUG. Signed-off-by: Milosz Tanski --- fs/ceph/addr.c |2 ++ fs/ceph/cache.h |7 +++ 2 files changed, 9 insertions(+) diff

[PATCH 3/8] fscache: Netfs function for cleanup post readpages

Currently the fscache code expect the netfs to call fscache_readpages_or_alloc inside the aops readpages callback. It marks all the pages in the list provided by readahead with PG_private_2. In the cases that the netfs fails to read all the pages (which is legal) it ends up returning to the

[PATCH 6/8] ceph: ceph_readpage_to_fscache didn't check if marked

Previously ceph_readpage_to_fscache did not call if page was marked as cached before calling fscache_write_page resulting in a BUG inside of fscache. FS-Cache: Assertion failed [ cut here ] kernel BUG at fs/fscache/page.c:874! invalid opcode: [#1] SMP Call Trace: []

[PATCH 2/8] CacheFiles: Implement interface to check cache consistency

Implement the FS-Cache interface to check the consistency of a cache object in CacheFiles. Original-author: Hongyi Jia Signed-off-by: David Howells cc: Hongyi Jia cc: Milosz Tanski --- fs/cachefiles/interface.c | 26 ++ fs/cachefiles/internal.h |1 +

[PATCH 1/8] FS-Cache: Add interface to check consistency of a cached object

Extend the fscache netfs API so that the netfs can ask as to whether a cache object is up to date with respect to its corresponding netfs object: int fscache_check_consistency(struct fscache_cookie *cookie) This will call back to the netfs to check whether the auxiliary data associated

[PATCH 0/8] ceph: fscache support & upstream changes

Hey gang I think this should be final revision of these changes. The changes are: * David rewrote the cookie validity check (that originally was written by Hongyi Jia). You might have seen some emails flying about doing it the right way. * I added crash fix when for Ceph filesystems

Re: [RFC PATCH 0/3] irq: Fix stack overflow due to softirq called on current stack

On Thu, 2013-09-05 at 17:33 +0200, Frederic Weisbecker wrote: > Hi, > > This series is a proposition to fix the crash reported here: > http://lkml.kernel.org/r/1378330796.4321.50.camel%40pasglop > And it has the upside to also consolidate a bit the arch do_softirq overriden > implementation. >

[GIT] [3.12] MFD pull request

Hi Linus, This is the MFD pull request for the 3.12 merge window. This time we have one new driver for the DA9063 PMIC from Dialog Semiconductor. Besides that driver we also have: - Device tree support for the s2mps11 driver - More devm_* conversion for the pm8921, max89xx, menelaus, tps65010,

Re: Excess dmesg output from ACPIPHP on boot (was: Re: [PATCH 25/30] ACPI / hotplug / PCI: Check for new devices on enabled slots)

On Thu, 2013-09-05 at 23:39 +0200, Rafael J. Wysocki wrote: > On Thursday, September 05, 2013 09:44:26 PM Rafael J. Wysocki wrote: > > On Thursday, September 05, 2013 08:21:41 AM Alex Williamson wrote: > > [...] > > > > > > > > > [ 18.288122] pci :00:00.0: no hotplug settings from

Re: [PATCH 2/2 v2] mm: allow to set overcommit ratio more precisely

hi! > >> This patch adds the new overcommit_ratio_ppm sysctl variable that > >> allow to set overcommit ratio with a part per million precision. > >> The old overcommit_ratio variable can still be used to set and read > >> the ratio with a 1% precision. That way, overcommit_ratio interface > >>

Re: [git pull] drm tree for 3.12-rc1

On Fri, Sep 6, 2013 at 5:18 AM, Linus Torvalds wrote: > On Thu, Sep 5, 2013 at 3:41 AM, Dave Airlie wrote: >> >> i915: Haswell PC8+ support and eLLC support, HDMI 4K support, initial >> per-process VMA pieces, >> watermark reworks, convert to generic hdmi infoframes, encoder >>

Re: more perf breakage from sample identifier

On 9/5/13 3:35 PM, David Ahern wrote: Adrian: 'perf kvm stat live' command fails on Linus' latest tree: $ perf kvm stat live Failed to parse sample git bisect points to: 75562573bab35b129cfd342fc2bcf89da84a6644 is the first bad commit commit 75562573bab35b129cfd342fc2bcf89da84a6644 Author:

[ 35/36] imx-drm: imx-drm-core: Export imx_drm_encoder_get_mux_id

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Fabio Estevam commit ea8d15832016b0d07a8121159904e6b1d21b5b8b upstream. When building imx_v6_v7_defconfig with imx-drm drivers selected as modules, we get the following build error: ERROR:

Re: [PATCH] rcu: Is it safe to enter an RCU read-side critical section?

On Thu, Sep 05, 2013 at 04:25:58PM -0400, Steven Rostedt wrote: > On Thu, 5 Sep 2013 12:52:34 -0700 > "Paul E. McKenney" wrote: > > > There is currently no way for kernel code to determine whether it > > is safe to enter an RCU read-side critical section, in other words, > > whether or not RCU

more perf breakage from sample identifier

Adrian: 'perf kvm stat live' command fails on Linus' latest tree: $ perf kvm stat live Failed to parse sample git bisect points to: 75562573bab35b129cfd342fc2bcf89da84a6644 is the first bad commit commit 75562573bab35b129cfd342fc2bcf89da84a6644 Author: Adrian Hunter Date: Tue Aug 27

Re: Excess dmesg output from ACPIPHP on boot (was: Re: [PATCH 25/30] ACPI / hotplug / PCI: Check for new devices on enabled slots)

On Thursday, September 05, 2013 11:39:07 PM Rafael J. Wysocki wrote: > On Thursday, September 05, 2013 09:44:26 PM Rafael J. Wysocki wrote: > > On Thursday, September 05, 2013 08:21:41 AM Alex Williamson wrote: > > [...] > > > > > > > > > [ 18.288122] pci :00:00.0: no hotplug settings

Re: [PATCH 25/30] ACPI / hotplug / PCI: Check for new devices on enabled slots

On Thursday, September 05, 2013 09:11:51 AM Lan Tianyu wrote: > 2013/9/5 Rafael J. Wysocki : > > On Thursday, September 05, 2013 02:17:06 PM Lan Tianyu wrote: > >> 2013/9/5 Alex Williamson : > >> > On Thu, 2013-09-05 at 01:35 +0200, Rafael J. Wysocki wrote: > >> >> On Wednesday, September 04, 2013

Re: [PATCH 08/10] fuse: use d_materialise_unique()

On Wed, Sep 04, 2013 at 04:05:54PM +0200, Miklos Szeredi wrote: > From: Miklos Szeredi > > Use d_materialise_unique() instead of d_splice_alias(). This allows dentry > subtrees to be moved to a new place if there moved, even if something is > referencing a dentry in the subtree (open fd, cwd,

[PATCH 2/2] thp: support split page table lock

Thp related code also uses per process mm->page_table_lock now. So making it fine-grained can provide better performance. This patch makes thp support split page table lock by using page->ptl of the pages storing "pmd_trans_huge" pmds. Some functions like pmd_trans_huge_lock() and

[PATCH 1/2] hugetlbfs: support split page table lock

Currently all of page table handling by hugetlbfs code are done under mm->page_table_lock. So when a process have many threads and they heavily access to the memory, lock contention happens and impacts the performance. This patch makes hugepage support split page table lock so that we use

[ 34/36] xen/arm: missing put_cpu in xen_percpu_init

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Julien Grall commit 0d7febe58413884f6428143221971618fbf3a47d upstream. When CONFIG_PREEMPT is enabled, Linux will not be able to boot and warn: [4.127825] [ cut here

[ 0/7] 3.0.95-stable review

This is the start of the stable review cycle for the 3.0.95 release. There are 7 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat Sep 7 20:27:46 UTC 2013. Anything

Re: [PATCH v4 3/5] clk: dt: binding for basic multiplexer clock

On 09/05/2013 12:29 PM, Mike Turquette wrote: > On Wed, Sep 4, 2013 at 11:36 AM, Stephen Warren wrote: >> On 09/03/2013 05:22 PM, Mike Turquette wrote: >>> Quoting Stephen Warren (2013-08-30 14:37:46) On 08/30/2013 02:33 PM, Mike Turquette wrote: >> ... > The clock _data_ seems to always

[PATCH 0/2 v3] split page table lock for hugepage

I revised the split ptl patchset with small fixes. See also the previous post [1] for the motivation and the numbers. Any comments and reviews are welcomed. [1] http://thread.gmane.org/gmane.linux.kernel.mm/106292/ Thanks, Naoya Horiguchi --- Summary: Naoya Horiguchi (2): hugetlbfs:

[ 28/36] iscsi-target: Fix potential NULL pointer in solicited NOPOUT reject

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit 28aaa950320fc7b8df3f6d2d34fa7833391a9b72 upstream. This patch addresses a potential NULL pointer dereference regression in iscsit_setup_nop_out() code, specifically

[ 04/36] ALSA: hda - Add inverted digital mic fixup for Acer Aspire One

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit d3d3835ce919438c00c5d1270d6f9d6ffea59d03 upstream. Yet another entry, just use the existing fixup for this machine, too. Reported-by: "Nathanael D. Noblet"

[ 06/36] powerpc: Work around gcc miscompilation of __pa() on 64-bit

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit bdbc29c19b2633b1d9c52638fb732bcde7a2031a upstream. On 64-bit, __pa(_var) gets miscompiled by recent versions of gcc as something like: addis

[ 32/36] ACPI / EC: Add ASUSTEK L4R to quirk list in order to validate ECDT

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Lan Tianyu commit 524f42fab787a9510be826ce3d736b56d454ac6d upstream. The ECDT of ASUSTEK L4R doesn't provide correct command and data I/O ports. The DSDT provides the correct information

[ 01/14] jfs: fix readdir cookie incompatibility with NFSv4

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Kleikamp commit 44512449c0ab368889dd13ae0031fba74ee7e1d2 upstream. NFSv4 reserves readdir cookie values 0-2 for special entries (. and ..), but jfs allows a value of 2 for a non-special

Re: Excess dmesg output from ACPIPHP on boot (was: Re: [PATCH 25/30] ACPI / hotplug / PCI: Check for new devices on enabled slots)

On Thursday, September 05, 2013 09:44:26 PM Rafael J. Wysocki wrote: > On Thursday, September 05, 2013 08:21:41 AM Alex Williamson wrote: [...] > > > > > > [ 18.288122] pci :00:00.0: no hotplug settings from platform > > > [ 18.288127] pcieport :00:01.0: no hotplug settings from

Re: [PATCH v2 1/1] dcache: Translating dentry into pathname without taking rename_lock

On Thu, Sep 5, 2013 at 1:46 PM, Al Viro wrote: > > static int prepend_name(char **buffer, int *buflen, struct qstr *name) > { > const char *s = ACCESS_ONCE(name->name); > unsigned len = ACCESS_ONCE(name->len); > char *p; > > *buflen -= len; > if (*buflen <

Re: kobject: delayed kobject release: help find buggy drivers

On Thu, Sep 05, 2013 at 05:11:13PM -0400, Dave Jones wrote: > > Trying without serial console next.. > > rebuilt with all serial turned off. > > no luck, then it oopses somewhere else. I'm suspecting something isn't > right with that debug patch, as the next trace is also in

Re: [PATCH v3 0/2] ext4: increase mbcache scalability

On 09/04/2013 08:00 PM, Andreas Dilger wrote: > > In the past, I've raised the question of whether mbcache is even > useful on real-world systems. Essentially, this is providing a > "deduplication" service for ext2/3/4 xattr blocks that are identical. > The question is how often this is actually

[GIT PULL] namespace chnages for 3.12

Linus, Please pull the for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-linus HEAD: c7b96acf1456ef127fef461fcfedb54b81fecfbb userns: Kill nsown_capable it makes the wrong thing easy This tree is against v3.11-rc1 This is an

Re: kobject: delayed kobject release: help find buggy drivers

On Thu, Sep 05, 2013 at 03:29:17PM -0400, Dave Jones wrote: > On Thu, Sep 05, 2013 at 06:35:40PM +0100, Russell King - ARM Linux wrote: > > > Dave - thanks for your patience and effort in trying to track this down. > > Hopefully the patch below will make it easier. > > I'm not sure if

Re: [PATCH] rcu: Is it safe to enter an RCU read-side critical section?

On Thu, Sep 05, 2013 at 01:59:59PM -0700, Paul E. McKenney wrote: > On Thu, Sep 05, 2013 at 04:25:58PM -0400, Steven Rostedt wrote: > > On Thu, 5 Sep 2013 12:52:34 -0700 > > "Paul E. McKenney" wrote: > > > > > There is currently no way for kernel code to determine whether it > > > is safe to

RE: RFC Block Layer Extensions to Support NV-DIMMs

Thanks! I understand that... However, unless transactional services are constructed lot of performance would be lost due to excessive commits of journals. This is specific for PM Regards, Boris > -Original Message- > From: Gittins, Rob [mailto:rob.gitt...@intel.com] > Sent:

Re: [PATCH v4 3/5] clk: dt: binding for basic multiplexer clock

On 09/05/2013 10:30 PM, Stephen Warren wrote: On 09/05/2013 12:29 PM, Mike Turquette wrote: > On Wed, Sep 4, 2013 at 11:36 AM, Stephen Warren wrote: >> On 09/03/2013 05:22 PM, Mike Turquette wrote: >>> Quoting Stephen Warren (2013-08-30 14:37:46) On 08/30/2013 02:33 PM, Mike

[ 17/36] drm/i915: ivb: fix edp voltage swing reg val

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Imre Deak commit 77fa4cbd5fa389e28419bbe8ac491b5fdd54840d upstream. Fix the typo introduced in commit 1a2eb4604b85c5efb343da8a4dcf41288fcfca85 Author: Keith Packard Date: Wed Nov 16

[ 15/36] workqueue: cond_resched() after processing each work item

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit b22ce2785d97423846206cceec4efee0c4afd980 upstream. If !PREEMPT, a kworker running work items back to back can hog CPU. This becomes dangerous when a self-requeueing work item

[GIT] Sparc

Several bug fixes (from Kirill Tkhai, Geery Uytterhoeven, and Alexey Dobriyan) and some support for Fujitsu sparc64x chips (from Allen Pais). Please pull, thanks a lot! The following changes since commit 64f8525fee499625b517c0faadf784c79e93: Merge branch 'drm-fixes' of

[ 00/36] 3.10.11-stable review

This is the start of the stable review cycle for the 3.10.11 release. There are 36 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat Sep 7 20:26:25 UTC 2013. Anything

[GIT] IDE

Mostly cleanups, and changes part of tree-wide adjustments, this code is in deep freeze so that's pretty much what we expect these days. Please pull, thanks a lot! The following changes since commit a09e9a7a4b907f2dfa9bdb2b98a1828ab4b340b2: Merge branch 'drm-next' of

[ 09/36] SCSI: pm80xx: fix Adaptec 71605H hang

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 9504a923924d663e1953f872f0a828e6454a6cfc upstream. The IO command size is 128 bytes for these new controllers as opposed to 64 for the old 8001 controller. The Adaptec

Re: [PATCH v2 1/1] dcache: Translating dentry into pathname without taking rename_lock

On Thu, Sep 05, 2013 at 04:29:06PM -0400, Waiman Long wrote: > It is not as simple as doing a strncpy(). The pathname was built > from the leaf up to the root, and from the end of buffer toward the > beginning. As it goes through the while loop, the buffer will look > like: > > "/c" > "

[ 11/36] timer_list: correct the iterator for timer_list

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Nathan Zimmer commit 84a78a6504f5c5394a8e558702e5b54131f01d14 upstream. Correct an issue with /proc/timer_list reported by Holger. When reading from the proc file with a sufficiently small

Re: [PATCH v2 1/1] dcache: Translating dentry into pathname without taking rename_lock

On Thu, Sep 5, 2013 at 1:29 PM, Waiman Long wrote: > > It is not as simple as doing a strncpy(). Yes it damn well is. Stop the f*cking stupid arguments, and instead listen to what I say. Here. Let me bold-face the most important part for you, so that you don't miss it in all the other crap:

[ 10/36] regmap: Add another missing header for !CONFIG_REGMAP stubs

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Kevin Hilman commit 3f0fa9a808f98fa10a18ba2a73f13d65fda990fb upstream. The use of WARN_ON() needs the definitions from bug.h, without it you can get: include/linux/regmap.h: In function

[ 12/36] IPC: bugfix for msgrcv with msgtyp < 0

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Svenning Soerensen commit 368ae537e056acd3f751fa276f48423f06803922 upstream. According to 'man msgrcv': "If msgtyp is less than 0, the first message of the lowest type that is less than or

[ 08/36] powerpc/hvsi: Increase handshake timeout from 200ms to 400ms.

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Eugene Surovegin commit d220980b701d838560a70de691b53be007e99e78 upstream. This solves a problem observed in kexec'ed kernel where 200ms timeout is too short and bootconsole fails to

Re: RFC Block Layer Extensions to Support NV-DIMMs

Hi Boris, The purpose of commitpmem is to notify the hardware that data is ready to be made persistent. This would mean flush any internal buffers and do whatever is needed in the hardware to ensure durable data. I was trying to keep the API simple to allow the application to build it's own

[ 03/36] ALSA: hda - Fix NULL dereference with CONFIG_SND_DYNAMIC_MINORS=n

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 2ca320e294a738c9134a71b5029de05edbfc7aad upstream. Without the dynamic minor assignment, HDMI codec may have less PCM instances than the number of pins, which eventually

[ 07/36] powerpc: Dont Oops when accessing /proc/powerpc/lparcfg without hypervisor

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit f5f6cbb61610b7bf9d9d96db9c3979d62a424bab upstream. /proc/powerpc/lparcfg is an ancient facility (though still actively used) which allows access to some

Re: [PATCH v2 1/1] dcache: Translating dentry into pathname without taking rename_lock

On 09/05/2013 04:04 PM, Al Viro wrote: On Thu, Sep 05, 2013 at 02:55:16PM -0400, Waiman Long wrote: + const char *dname = ACCESS_ONCE(dentry->d_name.name); + u32 dlen = dentry->d_name.len; + int error; + + if (likely(dname == (const char *)dentry->d_iname)) { +

[ 02/36] jfs: fix readdir cookie incompatibility with NFSv4

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Dave Kleikamp commit 44512449c0ab368889dd13ae0031fba74ee7e1d2 upstream. NFSv4 reserves readdir cookie values 0-2 for special entries (. and ..), but jfs allows a value of 2 for a non-special

[ 09/14] SUNRPC: Fix memory corruption issue on 32-bit highmem systems

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 347e2233b7667e336d9f671f1a52dfa3f0416e2c upstream. Some architectures, such as ARM-32 do not return the same base address when you call kmap_atomic() twice on the same

[ 18/36] SUNRPC: Fix memory corruption issue on 32-bit highmem systems

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 347e2233b7667e336d9f671f1a52dfa3f0416e2c upstream. Some architectures, such as ARM-32 do not return the same base address when you call kmap_atomic() twice on the same

[ 02/14] ALSA: opti9xx: Fix conflicting driver object name

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit fb615499f0ad28ed74201c1cdfddf9e64e205424 upstream. The recent commit to delay the release of kobject triggered NULL dereferences of opti9xx drivers. The cause is that all

[ 30/36] usb: acm gadget: Null termintate strings table

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Graham Williams commit d257221854f0b34cca3247e6c45344d0470f7398 upstream. The gadget strings table should be null terminated. usb_gadget_get_string() loops through the table expecting a null

[ 12/14] ACPI / EC: Add ASUSTEK L4R to quirk list in order to validate ECDT

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Lan Tianyu commit 524f42fab787a9510be826ce3d736b56d454ac6d upstream. The ECDT of ASUSTEK L4R doesn't provide correct command and data I/O ports. The DSDT provides the correct information

[ 07/14] drm/vmwgfx: Split GMR2_REMAP commands if they are to large

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Jakob Bornecrantz commit 6e4dcff3adbf25acb87e74500a58e3c07bdec40f upstream. This fixes the piglit test texturing/max-texture-size causing the VM to die due to a too large SVGA command.

[ 27/36] iscsi-target: Fix iscsit_transport reference leak during NP thread reset

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit c9a03c12464c851e691e8d5b6c9deba779c512e0 upstream. This patch fixes a bug in __iscsi_target_login_thread() where an explicit network portal thread reset ends up

[ 21/36] ath9k: Enable PLL fix only for AR9340/AR9330

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Sujith Manoharan commit 19c361608ce3e73f352e323262f7e0a8264be3af upstream. The PLL hang workaround is required only for AR9330 and AR9340. This issue was first observed on an AP121 and the

[ 13/14] target: Fix trailing ASCII space usage in INQUIRY vendor+model

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit ee60bddba5a5f23e39598195d944aa0eb2d455e5 upstream. This patch fixes spc_emulate_inquiry_std() to add trailing ASCII spaces for INQUIRY vendor + model fields following

[ 2/7] ALSA: opti9xx: Fix conflicting driver object name

3.0-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit fb615499f0ad28ed74201c1cdfddf9e64e205424 upstream. The recent commit to delay the release of kobject triggered NULL dereferences of opti9xx drivers. The cause is that all

[ 14/36] memcg: check that kmem_cache has memcg_params before accessing it

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Vagin commit 6f6b8951897e487ea6f77b90ea01f70a9c363770 upstream. If the system had a few memory groups and all of them were destroyed, memcg_limited_groups_array_size has non-zero

[ 20/36] ath9k_htc: Restore skb headroom when returning skb to mac80211

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Helmut Schaa commit d2e9fc141e2aa21f4b35ee27072d84e9aa6e2ba0 upstream. ath9k_htc adds padding between the 802.11 header and the payload during TX by moving the header. When handing the frame

[ 24/36] iwl4965: fix rfkill set state regression

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Stanislaw Gruszka commit b2fcc0aee58a3435566dd6d8501a0b32f28b upstream. My current 3.11 fix: commit 788f7a56fce1bcb2067b62b851a086fca48a0056 Author: Stanislaw Gruszka Date: Thu Aug 1

[ 00/14] 3.4.61-stable review

This is the start of the stable review cycle for the 3.4.61 release. There are 14 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat Sep 7 20:25:41 UTC 2013. Anything

[ 31/36] hwmon: (k10temp) Add support for Fam16h (Kabini)

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Wei Hu commit 30b146d1cb5e7560192057098eb705118bd5511f upstream. The temperature reporting interface stays the same, so we just add the PCI-ID to the list. Verified on AMD Olive Hill.

[ 06/14] drivers/base/memory.c: fix show_mem_removable() to handle missing sections

3.4-stable review patch. If anyone has any objections, please let me know. -- From: Russ Anderson commit 21ea9f5ace3a7317cc3ba1fbc749758021a83136 upstream. "cat /sys/devices/system/memory/memory*/removable" crashed the system. The problem is that show_mem_removable() is

[ 23/36] mac80211: add a flag to indicate CCK support for HT clients

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Felix Fietkau commit 2dfca312a91631311c1cf7c090246cc8103de038 upstream. brcm80211 cannot handle sending frames with CCK rates as part of an A-MPDU session. Other drivers may have issues too.

[ 16/36] drm/vmwgfx: Split GMR2_REMAP commands if they are to large

3.10-stable review patch. If anyone has any objections, please let me know. -- From: Jakob Bornecrantz commit 6e4dcff3adbf25acb87e74500a58e3c07bdec40f upstream. This fixes the piglit test texturing/max-texture-size causing the VM to die due to a too large SVGA command.

<    1   2   3   4   5   6   7   8   9   10   >