Re: [PATCH 05/13] overlayfs: add statfs support

On Thu, 2012-08-30 at 00:48 +0200, Miklos Szeredi wrote: > Ben Hutchings writes: > > > On Wed, Aug 15, 2012 at 05:48:12PM +0200, Miklos Szeredi wrote: > >> From: Andy Whitcroft > >> > >> Add support for statfs to the overlayfs filesystem. As the upper layer > >> is the target of all write

[git pull] drm fixes

Hi Linus, a bunch of scattered fixes ati/intel/nouveau, couple of core ones, nothing too shocking or different. Dave. The following changes since commit fea7a08acb13524b47711625eebea40a0ede69a0: Linux 3.6-rc3 (2012-08-22 13:29:06 -0700) are available in the git repository at:

[PATCH] MAINTAINERS: fix TXT maintainer list and source repo path

From: Gang Wei Signed-off-by: Gang Wei --- MAINTAINERS |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index fdc0119..987ad0f 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -3666,11 +3666,12 @@ F:

RE: [PATCH] usb: tegra: moving phy driver into drivers directory

> -Original Message- > From: linux-tegra-ow...@vger.kernel.org [mailto:linux-tegra- > ow...@vger.kernel.org] On Behalf Of Stephen Warren > Sent: Wednesday, August 29, 2012 11:01 PM > To: Venu Byravarasu > Cc: ccr...@android.com; o...@lixom.net; li...@arm.linux.org.uk; >

Which disk is ata4?

One of my disks went out to lunch for a while. Logs below. Which one is it? The only useful thing in /sys/class/ata_port/ata4 is the device symlink, which points at /sys/devices/pci:00/:00:1f.2/ata4. That, in turn, has an ata_port directory (contains nothing I don't already know) and a

[PATCH v6 1/1] ieee802154: MRF24J40 driver

Driver for the Microchip MRF24J40 802.15.4 WPAN module. Signed-off-by: Alan Ott --- drivers/ieee802154/Kconfig| 11 + drivers/ieee802154/Makefile |1 + drivers/ieee802154/mrf24j40.c | 767 + 3 files changed, 779 insertions(+), 0 deletions(-)

[PATCH v6 0/1] Driver for Microchip MRF24J40

This is a driver for the Microchip MRF24J40 802.15.4 transceiver. Versions 1-5 and discussion can be found on the archives of the linux-zigbee mailing list: http://www.mail-archive.com/linux-zigbee-devel@lists.sourceforge.net/msg01014.html Alan Ott (1): ieee802154: MRF24J40 driver

Re: Using uio_pdrv to create an platform device for an FPGA, mmap() fails

[Added driver author to Cc:] On Wed, Aug 29, 2012 at 11:19:00PM +, Worth, Kevin wrote: > I have below what appears to be a mostly-functional device using the UIO > Platform Driver. The /sys entries I'd expect appear, /proc/iomem contains " > d000-dfff : myfpga", and lsuio sees the

[PATCH v2 2/2] 6lowpan: handle NETDEV_UNREGISTER event

Before, it was impossible to remove a wpan device which had lowpan attached to it. Signed-off-by: Alan Ott --- net/ieee802154/6lowpan.c | 44 +--- 1 files changed, 37 insertions(+), 7 deletions(-) diff --git a/net/ieee802154/6lowpan.c

[PATCH v2 1/2] 6lowpan: Make a copy of skb's delivered to 6lowpan

Since lowpan_process_data() modifies the skb (by calling skb_pull()), we need our own copy so that it doesn't affect the data received by other protcols (in this case, af_ieee802154). Signed-off-by: Alan Ott --- net/ieee802154/6lowpan.c |9 - 1 files changed, 8 insertions(+), 1

[PATCH v2 0/2] 6lowpan fixes

Fixes for 6lowpan. I'm sorry about the other two emails that just went out with the same subject. One day I'm going to start getting these right on the first try. Alan Ott (2): 6lowpan: Make a copy of skb's delivered to 6lowpan 6lowpan: handle NETDEV_UNREGISTER event

Re: [PATCH 3/9 V3] workqueue: add POOL_MANAGING_WORKERS

On 08/30/2012 02:21 AM, Tejun Heo wrote: > Hello, Lai. > > On Thu, Aug 30, 2012 at 12:51:54AM +0800, Lai Jiangshan wrote: >> When hotplug happens, the plug code will also grab the manager_mutex, >> it will break too_many_workers()'s assumption, and make too_many_workers() >> ugly(kick the timer

[PATCH 2/2] 6lowpan: handle NETDEV_UNREGISTER event

Before, it was impossible to remove a wpan device which had lowpan attached to it. Signed-off-by: Alan Ott --- net/ieee802154/6lowpan.c | 44 +--- 1 files changed, 37 insertions(+), 7 deletions(-) diff --git a/net/ieee802154/6lowpan.c

[PATCH] 6lowpan: Make a copy of skb's delivered to 6lowpan

Since lowpan_process_data() modifies the skb (by calling skb_pull()), we need our own copy so that it doesn't affect the data received by other protcols (in this case, af_ieee802154). Signed-off-by: Alan Ott --- net/ieee802154/6lowpan.c |9 - 1 files changed, 8 insertions(+), 1

Re: [PATCH 0/2] Renesas IPMMU driver for sh7372

Hi Simon, On 2012/08/25 16:13, Simon Horman wrote: > On Wed, Jul 25, 2012 at 03:29:00PM +0900, Hideki EIRAKU wrote: >> This is the Renesas IPMMU driver, IOMMU API implementation and IPMMU >> device support for sh7372 (AP4EVB and Mackerel). >> >> The IPMMU module supports the MMU function and the

Re: [PATCH v10] kvm: notify host when the guest is panicked

At 08/29/2012 07:56 PM, Sasha Levin Wrote: > On 08/29/2012 07:18 AM, Wen Congyang wrote: >> We can know the guest is panicked when the guest runs on xen. >> But we do not have such feature on kvm. >> >> Another purpose of this feature is: management app(for example: >> libvirt) can do auto dump

Re: [PATCH v6] mmc: card: Skip secure option for MoviNAND.

Hi, On Wed, Aug 29 2012, IAN CHEN wrote: > Thanks for your help. > The effected kernel will be all the version with MMC_CAP_ERASE & SECURE > option enabled. > As commit content mentioned, the problem is unrecoverable corruption after > SECURE ERASE or SECURE TRIM. > For devices using defective

RE: [PATCH v6] mmc: card: Skip secure option for MoviNAND.

Hi, Thanks for your help. The effected kernel will be all the version with MMC_CAP_ERASE & SECURE option enabled. As commit content mentioned, the problem is unrecoverable corruption after SECURE ERASE or SECURE TRIM. For devices using defective eMMC with kernel supporting MMC_CAP_ERASE & SECURE

Re: [PATCH 6/7] net/netfilter/nfnetlink_log.c: fix error return code

On Wed, Aug 29, 2012 at 06:49:17PM +0200, Julia Lawall wrote: > From: Julia Lawall > > Initialize return variable before exiting on an error path. > > A simplified version of the semantic match that finds this problem is as > follows: (http://coccinelle.lip6.fr/) > > // > ( > if@p1 (\(ret <

Re: [PATCH 7/7] net/netfilter/nf_conntrack_netlink.c: fix error return code

On Wed, Aug 29, 2012 at 06:49:16PM +0200, Julia Lawall wrote: > From: Julia Lawall > > Initialize return variable before exiting on an error path. > > A simplified version of the semantic match that finds this problem is as > follows: (http://coccinelle.lip6.fr/) > > // > ( > if@p1 (\(ret <

Re: [PATCH 1/7] ipvs: fix error return code

On Wed, Aug 29, 2012 at 06:49:11PM +0200, Julia Lawall wrote: > From: Julia Lawall > > Initialize return variable before exiting on an error path. > > A simplified version of the semantic match that finds this problem is as > follows: (http://coccinelle.lip6.fr/) > > // > ( > if@p1 (\(ret <

Re: [PATCH v4] create sun sysfs file

Hi Len, Three weeks passed after I post the patch. All comments have already been applied to it. And I think there is no comments about it. So I want you to merge it into your tree. Thanks, Yasuaki Ishimatsu 2012/08/07 9:36, Yasuaki Ishimatsu wrote: > Even if a device has _SUN method, there is

Re: Drop support for x86-32

On Fri, 24 Aug 2012, Theodore Ts'o wrote: On Fri, Aug 24, 2012 at 11:17:20AM -0700, H. Peter Anvin wrote: Speaking as one of the x86 maintainers... we are currently deciding the cost/benefit tradeoff around removing i386 support. I don't mean general x86-32 support, I mean i386 as opposed to

Re: [PATCH 1/7] ipvs: fix error return code

On Wed, Aug 29, 2012 at 06:49:11PM +0200, Julia Lawall wrote: > From: Julia Lawall > > Initialize return variable before exiting on an error path. > > A simplified version of the semantic match that finds this problem is as > follows: (http://coccinelle.lip6.fr/) > > // > ( > if@p1 (\(ret <

CMA page migration failure due to buffers on bh_lru

Hi, I've been observing a high rate of failures with CMA allocations on my ARM system. I've set up a test case set up with a 56MB CMA region that essentially does the following: total_failures = 0; loop forever: loop_failure = 0; for (i = 0; i <

[PATCH] rpmsg: use right device paramter when calling dma_free_coherent function

dma_alloc/free_coherent APIs requires the platform specific remoteproc device as the device parameter. We are passing vdev->dev.parent to the dma_free_coherent function which is the generic rproc device and it is wrong, it has to be vdev->dev.parent->parent instead, same as when we call

Re: WARNING: at fs/inode.c:280 drop_nlink+0x31/0x33()

Thanks for replying Jeff... Yes, it sure would be great to have 3.5.z patch... --( Nick Pasich )-- On Wed, Aug 29, 2012 at 03:16:41PM -0700, Jeff Layton wrote: > On Wed, 29 Aug 2012 09:25:27 -0700 > Nick Pasich wrote: > > > > > I'm using kernel 3.5.3 ... > > > > It happens on 3.5.1 and

Re: [RFC/PATCH] ARM: smp: Fix cpu_up() racing with sys_reboot

On Tue, Aug 21, 2012 at 09:03:49PM -0700, Stephen Boyd wrote: > Nothing stops a process from hotplugging in a CPU concurrently > with a sys_reboot() call. In such a situation we could have > ipi_cpu_stop() mark a cpu as 'offline' and _cpu_up() ignore the > fact that the CPU is not really offline

Re: Drop support for x86-32

On Wed, Aug 29, 2012 at 7:03 PM, Mark Lord wrote: > On 12-08-26 10:15 AM, wbrana wrote: >> On 8/26/12, Mark Lord wrote: >>> Here are a couple of real scenarios you don't seem to have thought about. >>> A 32-bit kernel on a legacy (or even new) system in 2017 will still need >>> regular kernel

[PATCH 3/8] KVM: x86: mark opcode tables const

The opcode tables never change at runtime, therefor mark them const. Signed-off-by: Mathias Krause --- arch/x86/kvm/emulate.c | 40 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c index

[PATCH 2/8] KVM: x86 emulator: use aligned variants of SSE register ops

As the the compiler ensures that the memory operand is always aligned to a 16 byte memory location, use the aligned variant of MOVDQ for read_sse_reg() and write_sse_reg(). Signed-off-by: Mathias Krause --- arch/x86/kvm/emulate.c | 64 1 file

[PATCH 8/8] KVM: SVM: constify lookup tables

We never modify direct_access_msrs[], msrpm_ranges[], svm_exit_handlers[] or x86_intercept_map[] at runtime. Mark them r/o. Signed-off-by: Mathias Krause Cc: Joerg Roedel --- arch/x86/kvm/svm.c |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/x86/kvm/svm.c

[PATCH 7/8] KVM: VMX: constify lookup tables

We use vmcs_field_to_offset_table[], kvm_vmx_segment_fields[] and kvm_vmx_exit_handlers[] as lookup tables only -- make them r/o. Signed-off-by: Mathias Krause --- arch/x86/kvm/vmx.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/arch/x86/kvm/vmx.c

[PATCH 6/8] KVM: x86: more constification

Signed-off-by: Mathias Krause --- arch/x86/kvm/lapic.c |2 +- arch/x86/kvm/x86.c |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c index 18d149d..07ad628 100644 --- a/arch/x86/kvm/lapic.c +++ b/arch/x86/kvm/lapic.c @@

[PATCH 5/8] KVM: x86: constify read_write_emulator_ops

We never change those, make them r/o. Signed-off-by: Mathias Krause --- arch/x86/kvm/x86.c |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index f8b0148..79ac03c 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@

[PATCH 4/8] KVM: x86: constify emulate_ops

We never change emulate_ops[] at runtime so it should be r/o. Signed-off-by: Mathias Krause --- arch/x86/include/asm/kvm_emulate.h |2 +- arch/x86/kvm/emulate.c | 22 +++--- arch/x86/kvm/x86.c |2 +- 3 files changed, 13 insertions(+), 13

[PATCH 0/8] KVM: minor cleanups and optimizations

Hi Avi, Marcelo this patch series implements a few micro optimizations for the x86 KVM code base. The two major changes are constification of variables and an optimization for the SSE emulation. The former gives the compiler more opportunities for optimizations and ensures the r/o data is not put

[PATCH 1/8] KVM: x86: minor size optimization

Some fields can be constified and/or made static to reduce code and data size. Numbers for a 32 bit build: textdata bss dec hex filename before: 3351 80 03431 d67 cpuid.o after: 3391 0 03391 d3f cpuid.o Signed-off-by: Mathias

Using uio_pdrv to create an platform device for an FPGA, mmap() fails

I have below what appears to be a mostly-functional device using the UIO Platform Driver. The /sys entries I'd expect appear, /proc/iomem contains " d000-dfff : myfpga", and lsuio sees the properties that I've set. However an mmap() from userspace (either my test program below or

Re: Drop support for x86-32

On 12-08-26 10:15 AM, wbrana wrote: > On 8/26/12, Mark Lord wrote: >> Here are a couple of real scenarios you don't seem to have thought about. >> A 32-bit kernel on a legacy (or even new) system in 2017 will still need >> regular kernel updates (not "long term" un0maintained kernels) >> in order

Re: [PATCH v2 2/2] virtio-ring: Allocate indirect buffers from cache when possible

On Wed, Aug 29, 2012 at 10:46:19PM +0200, Sasha Levin wrote: > On 08/29/2012 08:12 PM, Michael S. Tsirkin wrote: > >>> > > What is a good default for net? I guess max sg? > >> > > >> > I think that it depends on the workload. I'd say we should keep the > >> > default to 0 > >> > (disabled)

Re: [PATCH 05/13] overlayfs: add statfs support

Ben Hutchings writes: > On Wed, Aug 15, 2012 at 05:48:12PM +0200, Miklos Szeredi wrote: >> From: Andy Whitcroft >> >> Add support for statfs to the overlayfs filesystem. As the upper layer >> is the target of all write operations assume that the space in that >> filesystem is the space in the

Re: WARNING: at fs/inode.c:280 drop_nlink+0x31/0x33()

On Wed, 29 Aug 2012 09:25:27 -0700 Nick Pasich wrote: > > I'm using kernel 3.5.3 ... > > It happens on 3.5.1 and 3.5.2 also. > > I know that Nick Bowler has already reported this... > > I'm experiencing the same thing. > > It happens when moving files from one directory to another > on the

[PATCH] staging: zcache: fix cleancache race condition with shrinker

This patch fixes a race condition that results in memory corruption when using cleancache. The race exists between the zcache shrinker handler, shrink_zcache_memory() and cleancache_get_page(). In most cases, the shrinker will both evict a zbpg from its buddy list and flush it from tmem before a

Storage regression in v3.6-rc3 was: Storage related regression in linux-next 20120824

Hi again, On 08/27/2012 06:39 PM, Dieter Ries wrote: > On 08/27/2012 04:40 PM, Jeff Garzik wrote: >> On Mon, Aug 27, 2012 at 4:59 AM, Arvydas Sidorenko wrote: >>> linux-next 20120824 introduced regression on Mac mini 2011 - /root partition >>> gets mounted as read-only and it stays so even when

Re: [PATCH] clk: Make the generic clock API available by default

On 08/28/12 13:35, Mark Brown wrote: Rather than requiring platforms to select the generic clock API to make it available make the API available as a user selectable option unless the user either selects HAVE_CUSTOM_CLK (if they have their own implementation) or selects COMMON_CLK (if they

Re: [PATCH 4/6] x86: Only direct map addresses that are marked as E820_RAM

On Wed, Aug 29, 2012 at 02:17:51PM -0700, Yinghai Lu wrote: > On Wed, Aug 29, 2012 at 12:04 PM, Jacob Shin wrote: > > Currently direct mappings are created for [ 0 to max_low_pfn< > and [ 4GB to max_pfn< > backed by actual DRAM. This is fine for holes under 4GB which are covered > > by fixed and

Re: [PATCH 4/6] x86: Only direct map addresses that are marked as E820_RAM

On Wed, Aug 29, 2012 at 02:17:51PM -0700, Yinghai Lu wrote: > > +struct range pfn_mapped[E820_X_MAX]; > > +int nr_pfn_mapped; > > change to static? > > > + > > +void add_pfn_range_mapped(unsigned long start_pfn, unsigned long end_pfn) > > +{ > > + nr_pfn_mapped =

[PATCH 1/2] module: allow loading module from fd

Instead of (or in addition to) kernel module signing, being able to reason about the origin of a kernel module would be valuable in situations where an OS already trusts a specific file system, file, etc, due to things like security labels or an existing root of trust to a partition through things

[PATCH 2/2] security: introduce kernel_module_from_file hook

Now that kernel module origins can be reasoned about, provide a hook to the LSMs to make policy decisions about the module file. Signed-off-by: Kees Cook --- include/linux/security.h | 11 +++ kernel/module.c |7 +++ security/capability.c|6 ++

Re: [PATCH 4/6] x86: Only direct map addresses that are marked as E820_RAM

On Wed, Aug 29, 2012 at 12:04 PM, Jacob Shin wrote: > Currently direct mappings are created for [ 0 to max_low_pfn< and [ 4GB to max_pfn< backed by actual DRAM. This is fine for holes under 4GB which are covered > by fixed and variable range MTRRs to be UC. However, we run into trouble > on

Re: [dm-devel] [PATCH v7 9/9] block: Avoid deadlocks with bio allocation by stacking drivers

> "Kent" == Kent Overstreet writes: Kent> On Wed, Aug 29, 2012 at 03:39:14PM +0100, Alasdair G Kergon wrote: >> It's also instructive to remember why the code is the way it is: it used >> to process bios for underlying devices immediately, but this sometimes >> meant too much recursive stack

Re: [dm-devel] [PATCH v7 9/9] block: Avoid deadlocks with bio allocation by stacking drivers

On Wed, Aug 29, 2012 at 05:01:09PM -0400, John Stoffel wrote: > > "Kent" == Kent Overstreet writes: > > Kent> On Wed, Aug 29, 2012 at 03:39:14PM +0100, Alasdair G Kergon wrote: > >> It's also instructive to remember why the code is the way it is: it used > >> to process bios for underlying

Re: [PATCH 5/6] x86: Fixup code testing if a pfn is direct mapped

On Wed, Aug 29, 2012 at 12:04 PM, Jacob Shin wrote: > Update code that previously assumed pfns [ 0 - max_low_pfn_mapped ) and > [ 4GB - max_pfn_mapped ) were always direct mapped, to now look up > pfn_mapped ranges instead. please swap patch 5 and patch 4 applying sequence. aka. should have

[PATCH][trivial] gen_init_cpio: remove redundant empty line

Just a completely trivial patch to remove a completely redundant blank line from usr/gen_init_cpio.c Signed-off-by: Jesper Juhl --- usr/gen_init_cpio.c | 1 - 1 file changed, 1 deletion(-) diff --git a/usr/gen_init_cpio.c b/usr/gen_init_cpio.c index af0f22f..b2e46bc 100644 ---

[PATCH] net: Providing protocol type via system.sockprotoname xattr of /proc/PID/fd entries

lsof reports some of socket descriptors as "can't identify protocol" like: [yamato@localhost]/tmp% sudo lsof | grep dbus | grep iden dbus-daem 652 dbus6u sock ... 17812 can't identify protocol dbus-daem 652 dbus 34u sock ... 24689 can't identify

Re: [PATCH v2 2/2] virtio-ring: Allocate indirect buffers from cache when possible

On 08/29/2012 08:12 PM, Michael S. Tsirkin wrote: >>> > > What is a good default for net? I guess max sg? >> > >> > I think that it depends on the workload. I'd say we should keep the >> > default to 0 >> > (disabled) unless we can have a good way to adjust it to the load. > For *all* drivers? >

Re: KS/Plumbers: c-state governor BOF

On 08/24/2012 01:01 PM, Rik van Riel wrote: Since a good number of us will be in San Diego next week, at Kernel Summit / Plumbers / etc, I will organize a c-state governor BOF for those who are interested. Here are the note from today's c-state governor BOF session: - idle time estimator can

Re: mxc_nand.c on mach-imx/imx53

Hi Roland, Le Wed, 29 Aug 2012 17:20:17 +0200, Roland Stigge a écrit : > Using ".ecclayout_4k = _hw_eccoob_4k" also doesn't work. So is > there any hint how I can proceed from here? Any plans or hint regarding > the "XXX"? > you may need something like this patch from barebox :

Re: [RFC 0/2] USB gadget - configfs

On 08/21/2012 10:19 AM, Andrzej Pietrasiewicz wrote: @Joel: However, I am wondering if it would make sense to get rid of the "connect" (or "ready", if you will) attribute altogether and instead use symlinks: when a user wants to make the gadget ready, they do an ln -s, when they want to unbind

Re: kernel 3.2.27 on arm: WARNING: at mm/page_alloc.c:2109 __alloc_pages_nodemask+0x1d4/0x68c()

David Madore : [...] > I imagine it being somehow related to the fact that it operates a > network bridge (I imagine this because I have another identical > machine with exactly the same kernel and a very similar config but not > running a bridge, and the warning never pops up). Could it not be

Re: "netpoll: re-enable irq in poll_napi()" breaks boot with netconsole

On Wed, Aug 29, 2012 at 02:59:47PM -0400, David Miller wrote: > From: Marcin Slusarz > Date: Wed, 29 Aug 2012 20:53:29 +0200 > > > Kernel 3.6-rc3 does not boot for me with netconsole enabled, while 3.6-rc2 > > did. > > I bisected it to commit 6bdb7fe31046ac50b47e83c35cd6c6b6160a475d "netpoll: >

[PATCH RFC 1/1] kvm: Use vcpu_id as pivot instead of last boosted vcpu in PLE handler

The idea of starting from next vcpu (source of yield_to + 1) seem to work well for overcomitted guest rather than using last boosted vcpu. We can also remove per VM variable with this approach. Iteration for eligible candidate after this patch starts from vcpu source+1 and ends at source-1

[PATCH 3.6-rc3 v2] wlcore: Declare MODULE_FIRMWARE usage

Declare any firmware that might be used by this driver. If all drivers declare their firmware usage, then a sufficiently complete list of firmware files can then be used to pare down the external linux-firmware package to just the files in actual use. Cc: Luciano Coelho Cc:

[PATCH 6/6] x86: if kernel .text .data .bss are not marked as E820_RAM, complain and fix

There could be cases where user supplied memmap=exactmap memory mappings do not mark the region where the kernel .text .data and .bss reside as E820_RAM, as reported here: https://lkml.org/lkml/2012/8/14/86 Handle it by complaining, and adding the range back into the e820. Signed-off-by: Jacob

[PATCH V5 0/6] x86: Create direct mappings for E820_RAM only

This is the 5th revision of the patchset, which aims to create direct mappings only for E820_RAM memory ranges. The problem description and justification can be found in patch 4/6. Previous discussion history can be found in the following threads: * https://lkml.org/lkml/2012/8/24/474 *

[PATCH 2/2] [2/2] extcon: optimising the check_mutually_exclusive function

From: anish kumar Rather than re-inventing the wheel we can use the hamming function to calculate the number of bits set to check for violation of exclusivity. Signed-off-by: anish kumar --- drivers/extcon/extcon-class.c | 14 +- 1 files changed, 5 insertions(+), 9 deletions(-)

[PATCH 5/6] x86: Fixup code testing if a pfn is direct mapped

Update code that previously assumed pfns [ 0 - max_low_pfn_mapped ) and [ 4GB - max_pfn_mapped ) were always direct mapped, to now look up pfn_mapped ranges instead. Signed-off-by: Jacob Shin --- arch/x86/kernel/cpu/amd.c |6 +- arch/x86/platform/efi/efi.c |8 2 files

[PATCH 1/2] [1/2]extcon: standard cable names definition and declaration changed

From: anish kumar With this change now individual drivers can use standard cable names as below: static const char *arizona_cable[] = { extcon_cable_name[EXTCON_USB], extcon_cable_name[EXTCON_USB_HOST], "CUSTOM_CABLE" NULL, } Signed-off-by: anish kumar ---

[PATCH 4/6] x86: Only direct map addresses that are marked as E820_RAM

Currently direct mappings are created for [ 0 to max_low_pfn< --- arch/x86/include/asm/page_types.h |9 arch/x86/kernel/setup.c | 100 +++-- arch/x86/mm/init.c|2 + arch/x86/mm/init_64.c |6 +-- 4 files

[PATCH 3/6] x86/mm: find_early_table_space based on memory ranges that are being mapped

Current logic finds enough space for direct mapping page tables from 0 to end. Instead, we only need to find enough space to cover mr[0].start to mr[nr_range].end -- the range that is actually being mapped by init_memory_mapping() This patch also reportedly fixes suspend/resume issue reported in:

[PATCH 2/6] x86, mm: Split out split_mem_range

From: Yinghai Lu from init_memory_mapping, so make init_memory_mapping readable. Suggested-by: Ingo Molnar Signed-off-by: Yinghai Lu --- arch/x86/mm/init.c | 42 ++ 1 file changed, 26 insertions(+), 16 deletions(-) diff --git a/arch/x86/mm/init.c

[PATCH 1/6] x86, mm: Add page_size_mask()

From: Yinghai Lu detect if need to use 1G or 2M and store them in page_size_mask. Only probe them one time. Suggested-by: Ingo Molnar Signed-off-by: Yinghai Lu --- arch/x86/include/asm/pgtable.h |1 + arch/x86/kernel/setup.c|1 + arch/x86/mm/init.c | 66

Re: "netpoll: re-enable irq in poll_napi()" breaks boot with netconsole

From: Marcin Slusarz Date: Wed, 29 Aug 2012 20:53:29 +0200 > Kernel 3.6-rc3 does not boot for me with netconsole enabled, while 3.6-rc2 > did. > I bisected it to commit 6bdb7fe31046ac50b47e83c35cd6c6b6160a475d "netpoll: > re-enable irq in poll_napi()" and reverting it on top of current Linus'

Re: [PATCH 3.6-rc3] wlcore: Declare MODULE_FIRMWARE usage

On Wed, 2012-08-29 at 11:13 -0600, Tim Gardner wrote: > On 08/29/2012 11:01 AM, Luciano Coelho wrote: > > On Wed, 2012-08-29 at 08:48 -0600, Tim Gardner wrote: > >> Cc: Luciano Coelho > >> Cc: "John W. Linville" > >> Cc: Eliad Peller > >> Cc: Arik Nemtsov > >> Cc: Eyal Shapira > >> Cc:

"netpoll: re-enable irq in poll_napi()" breaks boot with netconsole

Hi Kernel 3.6-rc3 does not boot for me with netconsole enabled, while 3.6-rc2 did. I bisected it to commit 6bdb7fe31046ac50b47e83c35cd6c6b6160a475d "netpoll: re-enable irq in poll_napi()" and reverting it on top of current Linus' tree restores proper behaviour (disabling netconsole does this

Re: Logitech USB headset not working in 3.6-rc3

On Wed, Aug 29, 2012 at 13:22:54 -0400, Josh Boyer wrote: On Wed, Aug 29, 2012 at 01:07:53PM -0400, Josh Boyer wrote: > Right. New patch attached. I'll try and get another kernel built with this later today. I'm at Plumbers so it might have to wait a bit. OK, I got impatient with myself

Re: [PATCH 8/9 V3] workqueue: single pass rebind_workers

Hello, Lai. On Thu, Aug 30, 2012 at 12:51:59AM +0800, Lai Jiangshan wrote: > busy_worker_rebind_fn() can't return until all idle workers are rebound, > the code of busy_worker_rebind_fn() ensure this. > > So we can change the order of the code of rebind_workers(), > and make it is a single pass

Re: i2c-eg20t: regression since i2c_add_numbered_adapter change

Hi guys, Sorry for joining the discussion a little late, I was on vacation. On Thu, 23 Aug 2012 16:28:52 +0800, Feng Tang wrote: > On Wed, 22 Aug 2012 11:17:51 +0200 > Alexander Stein wrote: > > Am Mittwoch, 22. August 2012, 16:04:39 schrieb Feng Tang: > > > > Why use a fixed one? Give the

Re: [PATCH 7/9 V3] workqueue: explicit way to wait for idles workers to finish

Hello, On Thu, Aug 30, 2012 at 12:51:58AM +0800, Lai Jiangshan wrote: > busy_worker_rebind_fn() can't return until all idle workers are rebound. > This order is ensured by rebind_workers() currently. > > We use mutex_lock(>pool->manager_mutex) to wait for all idle workers > to be rebound. this

Re: [PATCH 4/9 V3] workqueue: add non_manager_role_manager_mutex_unlock()

On Thu, Aug 30, 2012 at 12:51:55AM +0800, Lai Jiangshan wrote: > If hotplug code grabbed the manager_mutex and worker_thread try to create > a worker, the manage_worker() will return false and worker_thread go to > process work items. Now, on the CPU, all workers are processing work items, > no

Re: [PATCH 4/7] net/bluetooth/rfcomm/core.c: fix error return code

Hi Julia, > Initialize return variable before exiting on an error path. > > A simplified version of the semantic match that finds this problem is as > follows: (http://coccinelle.lip6.fr/) > > // > ( > if@p1 (\(ret < 0\|ret != 0\)) > { ... return ret; } > | > ret@p1 = 0 > ) > ... when != ret

Re: [PATCH 3/9 V3] workqueue: add POOL_MANAGING_WORKERS

Hello, Lai. On Thu, Aug 30, 2012 at 12:51:54AM +0800, Lai Jiangshan wrote: > When hotplug happens, the plug code will also grab the manager_mutex, > it will break too_many_workers()'s assumption, and make too_many_workers() > ugly(kick the timer wrongly, no found bug). > > To avoid

Re: [PATCH v2 2/2] virtio-ring: Allocate indirect buffers from cache when possible

On Wed, Aug 29, 2012 at 07:14:01PM +0200, Sasha Levin wrote: > On 08/29/2012 05:38 PM, Michael S. Tsirkin wrote: > > On Tue, Aug 28, 2012 at 03:04:03PM +0200, Sasha Levin wrote: > >> Currently if VIRTIO_RING_F_INDIRECT_DESC is enabled we will > >> use indirect descriptors and allocate them using a

Re: [PATCH 4/5] i2c-i801: Add Device IDs for Intel Lynx Point-LP PCH

Hi James, Quite a long Cc list for such a trivial patch... On Thu, 9 Aug 2012 09:43:52 -0700, james.d.rals...@intel.com wrote: > From: James Ralston > > This patch adds the SMBus Device IDs for the Intel Lynx Point-LP PCH. The > Device IDs are defined in drivers/i2c/busses/i2c-i801.c I'm

[GIT PULL] (Was: uprobes: teach uprobes to clear MMF_HAS_UPROBES)

On 08/27, Oleg Nesterov wrote: > > Srikar, this is still waiting for your review ;) I was informed that Srikar is travelling and can't review this seris. So I think it doesn't make sense to delay the already acked patches, the more testing the better ;) Yes, uprobe_munmap() looks strange, we

Re: [Linaro-mm-sig] [PATCH 2/4] dma-fence: dma-buf synchronization (v8 )

Hi, On Fri, Aug 10, 2012 at 4:57 PM, Maarten Lankhorst wrote: [Snip] > diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h > new file mode 100644 > index 000..e0ceddd > --- /dev/null > +++ b/include/linux/dma-fence.h > @@ -0,0 +1,124 @@ > +/* > + * Fence mechanism for

Re: [PATCH] block: Fix bad range check in bio_sector_offset

"Martin K. Petersen" writes: >> "Jeff" == Jeff Moyer writes: > >>> DM would occasionally end up splitting data integrity-enabled >>> requests incorrectly. The culprit was a bad range check in >>> bio_sector_offset. > > Jeff> The patch looks ok to me, but what is the user visible behavior >

Re: [PATCH 0/2] revert changes to zcache_do_preload()

Forget this whole thing, these reverts do _not_ fix the issue. I wrote a test program to exercises cleancache and determined that this problem has existed since the as far back at v3.1 (basically the beginning). No recent commit caused this. Seth -- To unsubscribe from this list: send the line

Re: HDD problem, software bug, bios bug, or hardware ?

And one more thing i forgot - during kernel compilation i noticed this: WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' And when i compiled with "make CONFIG_DEBUG_SECTION_MISMATCH=y", somewhere at the end was:

Re: [PATCH V2] regulator: tps6586x: register regulator even if no init data

On 08/29/12 08:01, Laxman Dewangan wrote: Register all TPS6586x regulators even if there is no regulator init data for platform i.e. without any user-supplied constraints. I think this looks OK now, although I would like to test it, and check for any interactions etc. with the other TPS6586x

Re: [PATCH -v12 02/15] resources: Add probe_resource()

On Wed, Aug 29, 2012 at 8:57 AM, Yinghai Lu wrote: > also have another version for probe_resource, please check attached version > -v8. > sorry, v8 forget removing two lines. please -v9 instead. -v8: Linus said: allocation/return is not right, and -1 step tricks make it not work as

Re: [PATCH v3] x86/uprobes: implement x86 specific arch_uprobe_*_step

On 08/22, Oleg Nesterov wrote: > > > Ehm. Is there anything I missed to do? Or are you speculating on > > changes which will clash with these here? > > If we have task_set_blockstep(), then perhaps it mmakes sense to > avoid user_enable_singlestep()/TIF_SINGLESTEP from the start. > We will see.

Re: [dm-devel] [PATCH v7 9/9] block: Avoid deadlocks with bio allocation by stacking drivers

On Wed, Aug 29, 2012 at 06:23:36PM +0100, Alasdair G Kergon wrote: > On Wed, Aug 29, 2012 at 10:13:45AM -0700, Kent Overstreet wrote: > > Only on allocation failure. > > Which as you already said assumes wrapping together the other mempools in the > submission path first... Yes? I'm not sure

Re: [PATCH] usb: tegra: moving phy driver into drivers directory

On 08/28/12 22:17, Venu Byravarasu wrote: Stephen Warren wrote at Tuesday, August 28, 2012 7:37 PM: On 08/28/2012 02:32 AM, Venu Byravarasu wrote: In order to keep up with the USB driver files organization, moving USB phy driver from mach-tegra to drivers/USB directory. Signed-off-by: Venu

Re: [PATCH 1/1] tcp: Wrong timeout for SYN segments

Eric, On Wed, Aug 29, 2012 at 1:51 AM, Eric Dumazet wrote: > On Tue, 2012-08-28 at 21:34 -0700, H.K. Jerry Chu wrote: > >> IMHO 31secs seem a little short. Why not change it to 6 as well because 63 >> secs still beats 93secs with 3sec initRTO and 5 retries. >> >> Jerry >> > > My rationale was

Re: [dm-devel] [PATCH v7 9/9] block: Avoid deadlocks with bio allocation by stacking drivers

On Wed, Aug 29, 2012 at 10:13:45AM -0700, Kent Overstreet wrote: > Only on allocation failure. Which as you already said assumes wrapping together the other mempools in the submission path first... Alasdair -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

Re: Logitech USB headset not working in 3.6-rc3

On Wed, Aug 29, 2012 at 01:07:53PM -0400, Josh Boyer wrote: > > Right. New patch attached. > > I'll try and get another kernel built with this later today. I'm at > Plumbers so it might have to wait a bit. OK, I got impatient with myself and got the kernel building sooner than I said. Bruno,

Re: [PATCH v2] HID: multitouch: Remove the redundant touch state

On Wed, 29 Aug 2012, Benjamin Tissoires wrote: > >> With the input_mt_sync_frame() function in place, there is no longer > >> any need to keep the full touch state in the driver. This patch > >> removes the slot state and replaces the lookup code with the input-mt > >> equivalent. The

Re: [PATCH] block: Fix bad range check in bio_sector_offset

On 2012-08-28 11:03, Martin K. Petersen wrote: > > DM would occasionally end up splitting data integrity-enabled requests > incorrectly. The culprit was a bad range check in bio_sector_offset. > > Signed-off-by: Martin K. Petersen > Cc: > > diff --git a/fs/bio.c b/fs/bio.c > index

  1   2   3   4   5   6   >