Re: [PATCH] memcg: fix hotplugged memory zone oops

On Fri 02-11-12 16:37:37, Hugh Dickins wrote: > On Fri, 2 Nov 2012, Michal Hocko wrote: > > On Fri 02-11-12 11:21:59, Michal Hocko wrote: > > > On Thu 01-11-12 18:28:02, Hugh Dickins wrote: > > [...] > > > > And I forgot to mention that the following hunk will clash with > > "memcg: Simplify mem_c

Re: [ 044/218] Staging: Android alarm: IOCTL command encoding fix

On Fri, Sep 28, 2012 at 1:14 PM, Greg Kroah-Hartman wrote: > 3.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: "Dae S. Kim" > > commit 6bd4a5d96c08dc2380f8053b1bd4f879f55cd3c9 upstream. > > Fixed a bug. Data was being written to user spac

[PATCH 0/3] ACPI 5 support for GPIO, SPI and I2C

Hi, With ACPI 5 we can now describe how devices are connected to their bus using new resources: SPISerialBus and I2CSerialBus. Also it is now possible to add GPIO connections for the devices with the help of GpioIO and GpioInt resources. This series adds support for these new resources. The seri

[PATCH 3/3] i2c / ACPI: add ACPI enumeration support

ACPI 5 introduced I2cSerialBus resource that makes it possible to enumerate and configure the I2C slave devices behind the I2C controller. This patch adds helper functions to support I2C slave enumeration. An ACPI enabled I2C controller driver only needs to call acpi_i2c_register_devices() in ord

[PATCH 1/3] gpio / ACPI: add ACPI support

From: Mathias Nyman Add support for translating ACPI GPIO pin numbers to Linux GPIO API pins. Needs a gpio controller driver with the acpi handler hook set. Drivers can use acpi_get_gpio() to translate ACPI5 GpioIO and GpioInt resources to Linux GPIO's. Signed-off-by: Mathias Nyman Signed-off-

[PATCH 2/3] spi / ACPI: add ACPI enumeration support

ACPI 5 introduced SPISerialBus resource that allows us to enumerate and configure the SPI slave devices behind the SPI controller. This patch adds support for this to the SPI core. In addition we bind ACPI nodes to SPI devices. This makes it possible for the slave drivers to get the ACPI handle fo

Re: [PATCH 0/3] Volatile Ranges (v7) & Lots of words

[CC += linux-api, since this is an API change.] Hi John, A couple of other questions that occurred to me... What are the expected/planned semantics of volatile ranges for mlocked pages? I noticed that Minchan's patch series (https://lwn.net/Articles/522154/) gives an error on attempt to mark loc

Is this a kernel bug?

Recent days we got a exception in kernel thread [kworker/n:m], but exception handler call do_group_exit() -> do_exit() -> schedule() and got another exception in schedule(): /* * If a worker is going to sleep, notify and * as

Re: [PATCH v2 1/9] net: core: use this_cpu_ptr per-cpu helper

On Fri, Nov 02, 2012 at 05:44:55PM +, Christoph Lameter wrote: > On Sat, 3 Nov 2012, Shan Wei wrote: > > +++ b/net/core/flow.c > > @@ -327,11 +327,9 @@ static void flow_cache_flush_tasklet(unsigned long > > data) > > static void flow_cache_flush_per_cpu(void *data) > > { > > struct flow_

Re: [PATCH v2 5/9] kernel: padata : use this_cpu_read per-cpu helper

> > @@ -204,8 +204,7 @@ static struct padata_priv *padata_get_next(struct > parallel_data *pd) > goto out; > } > > - queue = per_cpu_ptr(pd->pqueue, smp_processor_id()); > - if (queue->cpu_index == next_queue->cpu_index) { > + if (this_cpu_read(pd->pqueue->cpu_i

Re: BUG: enabling psacct breaks fsfreeze

Il 02/11/2012 11:40, Nikola Ciprich ha scritto: I saw this behavior (task-hang) when I tested the fsfreeze code. I was writing a little patch to replace fsfreeze's wait queue with a killable queue, in this way the user can do at least "kill -9", but since the behavior was the same before your pat

[PATCH v4 0/6] solve deadlock caused by memory allocation with I/O

This patchset try to solve one deadlock problem which might be caused by memory allocation with block I/O during runtime PM and block device error handling path. Traditionly, the problem is addressed by passing GFP_NOIO statically to mm, but that is not a effective solution, see detailed descriptio

[PATCH v4 1/6] mm: teach mm by current context info to not do I/O during memory allocation

This patch introduces PF_MEMALLOC_NOIO on process flag('flags' field of 'struct task_struct'), so that the flag can be set by one task to avoid doing I/O inside memory allocation in the task's context. The patch trys to solve one deadlock problem caused by block device, and the problem may happen

[PATCH v4 2/6] PM / Runtime: introduce pm_runtime_set_memalloc_noio()

The patch introduces the flag of memalloc_noio in 'struct dev_pm_info' to help PM core to teach mm not allocating memory with GFP_KERNEL flag for avoiding probable deadlock. As explained in the comment, any GFP_KERNEL allocation inside runtime_resume() or runtime_suspend() on any one of device in

[PATCH v4 3/6] block/genhd.c: apply pm_runtime_set_memalloc_noio on block devices

This patch applyes the introduced pm_runtime_set_memalloc_noio on block device so that PM core will teach mm to not allocate memory with GFP_IOFS when calling the runtime_resume and runtime_suspend callback for block devices and its ancestors. Cc: Jens Axboe Signed-off-by: Ming Lei --- v4:

[PATCH v4 4/6] net/core: apply pm_runtime_set_memalloc_noio on network devices

Deadlock might be caused by allocating memory with GFP_KERNEL in runtime_resume and runtime_suspend callback of network devices in iSCSI situation, so mark network devices and its ancestor as 'memalloc_noio' with the introduced pm_runtime_set_memalloc_noio(). Cc: "David S. Miller" Cc: Eric Dumaze

[PATCH v4 5/6] PM / Runtime: force memory allocation with no I/O during Runtime PM callbcack

This patch applies the introduced memalloc_noio_save() and memalloc_noio_restore() to force memory allocation with no I/O during runtime_resume/runtime_suspend callback on device with the flag of 'memalloc_noio' set. Cc: Alan Stern Cc: Oliver Neukum Cc: Rafael J. Wysocki Signed-off-by: Ming Lei

[PATCH v4 6/6] USB: forbid memory allocation with I/O during bus reset

If one storage interface or usb network interface(iSCSI case) exists in current configuration, memory allocation with GFP_KERNEL during usb_device_reset() might trigger I/O transfer on the storage interface itself and cause deadlock because the 'us->dev_mutex' is held in .pre_reset() and the storag

[PATCHSET cgroup/for-3.8] cgroup_freezer: implement proper hierarchy support

Hello, This patchset implement proper hierarchy support for cgroup_freezer as discussed in "[RFC] cgroup TODOs"[1]. The patchset first implements generic cgroup iteration macros - cgroup_for_each_children(), cgroup_for_each_descendant_{pre|post}(). Combined with the newly introduced ->post_create

[PATCH 1/9] cgroup: add cgroup_subsys->post_create()

Currently, there's no way for a controller to find out whether a new cgroup finished all ->create() allocatinos successfully and is considered "live" by cgroup. This becomes a problem later when we add generic descendants walking to cgroup which can be used by controllers as controllers don't have

[PATCH 2/9] cgroup: Use rculist ops for cgroup->children

Use RCU safe list operations for cgroup->children. This will be used to implement cgroup children / descendant walking which can be used by controllers. Note that cgroup_create() now puts a new cgroup at the end of the ->children list instead of head. This isn't strictly necessary but is done so

[PATCH 7/9] cgroup_freezer: introduce CGROUP_FREEZING_[SELF|PARENT]

Introduce FREEZING_SELF and FREEZING_PARENT and make FREEZING OR of the two flags. This is to prepare for full hierarchy support. freezer_apply_date() is updated such that it can handle setting and clearing of both flags. The two flags are also exposed to userland via read-only files self_freezi

[PATCH 9/9] cgroup_freezer: implement proper hierarchy support

Up until now, cgroup_freezer didn't implement hierarchy properly. cgroups could be arranged in hierarchy but it didn't make any difference in how each cgroup_freezer behaved. They all operated separately. This patch implements proper hierarchy support. If a cgroup is frozen, all its descendants

[PATCH 5/9] cgroup_freezer: prepare freezer_change_state() for full hierarchy support

* Make freezer_change_state() take bool @freeze instead of enum freezer_state. * Separate out freezer_apply_state() out of freezer_change_state(). This makes freezer_change_state() a rather silly thin wrapper. It will be filled with hierarchy handling later on. This patch doesn't introduce

[PATCH 4/9] cgroup_freezer: trivial cleanups

* Clean-up indentation and line-breaks. Drop the invalid comment about freezer->lock. * Make all internal functions take @freezer instead of both @cgroup and @freezer. Signed-off-by: Tejun Heo --- kernel/cgroup_freezer.c | 41 +++-- 1 file changed, 19 in

[PATCH 8/9] cgroup_freezer: add ->post_create() and ->pre_destroy() and track online state

A cgroup is online and visible to iteration between ->post_create() and ->pre_destroy(). This patch introduces CGROUP_FREEZER_ONLINE and toggles it from the newly added freezer_post_create() and freezer_pre_destroy() while holding freezer->lock such that a cgroup_freezer can be reilably distinguis

[PATCH 6/9] cgroup_freezer: make freezer->state mask of flags

freezer->state was an enum value - one of THAWED, FREEZING and FROZEN. As the scheduled full hierarchy support requires more than one freezing condition, switch it to mask of flags. If FREEZING is not set, it's thawed. FREEZING is set if freezing or frozen. If frozen, both FREEZING and FROZEN ar

[PATCH 3/9] cgroup: implement generic child / descendant walk macros

Currently, cgroup doesn't provide any generic helper for walking a given cgroup's children or descendants. This patch adds the following three macros. * cgroup_for_each_child() - walk immediate children of a cgroup. * cgroup_for_each_descendant_pre() - visit all descendants of a cgroup in pre-

[PATCH] IRQ CORE: irq_work_queue function return value not used.

From: anish kumar As no one is using the return value of irq_work_queue function it is better to just make it void. Acked-by: Steven Rostedt Signed-off-by: anish kumar --- kernel/irq_work.c |5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/kernel/irq_work.c b/kernel

Re: [PATCH v2 6/9] rcu: use __this_cpu_read helper instead of per_cpu_ptr(p, raw_smp_processor_id())

On Fri, Nov 02, 2012 at 08:19:04PM +, Christoph Lameter wrote: > On Fri, 2 Nov 2012, Paul E. McKenney wrote: > > > On Sat, Nov 03, 2012 at 12:01:47AM +0800, Shan Wei wrote: > > > From: Shan Wei > > > > > > Signed-off-by: Shan Wei > > > --- > > > kernel/rcutree.c |2 +- > > > 1 files cha

[PATCH 00/21 v4] drop vmtruncate

Hi all, I send the fourth patch series to remove vmtruncate. Any comments/feedback are welcome. Changes: v4: fix an error for ocfs2, silently ignore truncate for procfs as suggested by Al v3: reworked after Al and Christoph comments v2: add documentation cleaning v1: first draft Marco Storn

[PATCH 01/21] ufs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/ufs/inode.c | 15 ++- 1 files changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c index eb6d0b7..ff24e44 100644 --- a/fs/ufs/inode.c +++ b/fs/ufs/inode.c @@ -526,6 +526,14 @@ int ufs_prepar

[PATCH 02/21] sysv: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/sysv/file.c |5 +++-- fs/sysv/itree.c | 17 - 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/fs/sysv/file.c b/fs/sysv/file.c index 0a65939..9d4dc68 100644 --- a/fs/sysv/file.c +++ b/fs/sysv/file.c @@

[PATCH 03/21] reiserfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/reiserfs/file.c |3 +-- fs/reiserfs/inode.c| 15 +++ fs/reiserfs/reiserfs.h |1 + 3 files changed, 13 insertions(+), 6 deletions(-) diff --git a/fs/reiserfs/file.c b/fs/reiserfs/file.c index 8375c92..50302d6

[PATCH 04/21] procfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/proc/base.c|7 --- fs/proc/generic.c |9 + fs/proc/proc_sysctl.c |7 --- 3 files changed, 1 insertions(+), 22 deletions(-) diff --git a/fs/proc/base.c b/fs/proc/base.c index 144a967..6f009a3 100644

[PATCH 05/21] omfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/omfs/file.c | 22 +++--- 1 files changed, 15 insertions(+), 7 deletions(-) diff --git a/fs/omfs/file.c b/fs/omfs/file.c index 77e3cb2..e0d9b3e 100644 --- a/fs/omfs/file.c +++ b/fs/omfs/file.c @@ -306,6 +306,16 @@ omfs_wr

[PATCH 06/21] ocfs2: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/ocfs2/file.c | 18 -- 1 files changed, 0 insertions(+), 18 deletions(-) diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c index 5a4ee77..03f0d08 100644 --- a/fs/ocfs2/file.c +++ b/fs/ocfs2/file.c @@ -1218,24 +1218,6 @@ int

[PATCH 07/21] adfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/adfs/inode.c | 15 ++- 1 files changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/adfs/inode.c b/fs/adfs/inode.c index e9bad50..5f95d1e 100644 --- a/fs/adfs/inode.c +++ b/fs/adfs/inode.c @@ -45,6 +45,14 @@ static int

[PATCH 08/21] affs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/affs/file.c | 18 -- fs/affs/inode.c |5 - 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/fs/affs/file.c b/fs/affs/file.c index 2f4c935..af3261b 100644 --- a/fs/affs/file.c +++ b/fs/affs/file.c @

[PATCH 09/21] bfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/bfs/file.c | 15 ++- 1 files changed, 10 insertions(+), 5 deletions(-) diff --git a/fs/bfs/file.c b/fs/bfs/file.c index f20e8a7..ad3ea14 100644 --- a/fs/bfs/file.c +++ b/fs/bfs/file.c @@ -161,6 +161,14 @@ static int bfs_read

[PATCH 10/21] hfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/hfs/inode.c | 26 ++ 1 files changed, 18 insertions(+), 8 deletions(-) diff --git a/fs/hfs/inode.c b/fs/hfs/inode.c index 0b35903..d47f116 100644 --- a/fs/hfs/inode.c +++ b/fs/hfs/inode.c @@ -35,6 +35,16 @@ stati

[PATCH 11/21] hpfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/hpfs/file.c | 18 -- fs/hpfs/inode.c |5 - 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/fs/hpfs/file.c b/fs/hpfs/file.c index 89d2a58..e7629f7 100644 --- a/fs/hpfs/file.c +++ b/fs/hpfs/file.c @

[PATCH 12/21] jfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/jfs/file.c |6 -- fs/jfs/inode.c | 20 ++-- 2 files changed, 18 insertions(+), 8 deletions(-) diff --git a/fs/jfs/file.c b/fs/jfs/file.c index 9d3afd1..dd7442c 100644 --- a/fs/jfs/file.c +++ b/fs/jfs/file.c @@ -

[PATCH 13/21] hfsplus: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/hfsplus/inode.c | 27 --- 1 files changed, 16 insertions(+), 11 deletions(-) diff --git a/fs/hfsplus/inode.c b/fs/hfsplus/inode.c index 2172aa5..799b336 100644 --- a/fs/hfsplus/inode.c +++ b/fs/hfsplus/inode.c @@

[PATCH 14/21] logfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/logfs/readwrite.c | 10 -- 1 files changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/logfs/readwrite.c b/fs/logfs/readwrite.c index e1a3b6b..9a59cba 100644 --- a/fs/logfs/readwrite.c +++ b/fs/logfs/readwrite.c @@ -1887,9

[PATCH 15/21] minix: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/minix/file.c |6 -- fs/minix/inode.c | 17 - 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/fs/minix/file.c b/fs/minix/file.c index 4493ce6..adc6f54 100644 --- a/fs/minix/file.c +++ b/fs/minix/fi

[PATCH 16/21] ncpfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/ncpfs/inode.c |4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/fs/ncpfs/inode.c b/fs/ncpfs/inode.c index d7e9fe7..1acdad7 100644 --- a/fs/ncpfs/inode.c +++ b/fs/ncpfs/inode.c @@ -976,9 +976,7 @@ int ncp_notify_ch

[PATCH 17/21] nilfs2: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/nilfs2/file.c |1 - fs/nilfs2/inode.c| 24 +++- fs/nilfs2/nilfs.h|1 + fs/nilfs2/recovery.c |3 ++- 4 files changed, 18 insertions(+), 11 deletions(-) diff --git a/fs/nilfs2/file.c b/fs/nilfs2

[PATCH 18/21] ntfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/ntfs/file.c | 16 +--- fs/ntfs/inode.c |8 ++-- fs/ntfs/inode.h |4 3 files changed, 23 insertions(+), 5 deletions(-) diff --git a/fs/ntfs/file.c b/fs/ntfs/file.c index 1ecf464..5b2d4f0 100644 --- a/fs/ntfs

[PATCH 19/21] vfs: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- fs/libfs.c |2 -- include/linux/fs.h |1 - 2 files changed, 0 insertions(+), 3 deletions(-) diff --git a/fs/libfs.c b/fs/libfs.c index 7cc37ca..c8fe267 100644 --- a/fs/libfs.c +++ b/fs/libfs.c @@ -369,8 +369,6 @@ int simple_s

[PATCH 20/21] mm: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- include/linux/mm.h |1 - mm/truncate.c | 23 --- 2 files changed, 0 insertions(+), 24 deletions(-) diff --git a/include/linux/mm.h b/include/linux/mm.h index fa06804..95f70bb 100644 --- a/include/linux/mm.h +++

[PATCH 21/21] documentation: drop vmtruncate

Removed vmtruncate Signed-off-by: Marco Stornelli --- Documentation/filesystems/Locking |6 -- Documentation/filesystems/porting |2 +- Documentation/filesystems/vfs.txt | 11 --- 3 files changed, 1 insertions(+), 18 deletions(-) diff --git a/Documentation/filesystems/Lock

[PATCH] hid-apple.c: Set APPLE_ISO_KEYBOARD at USB_DEVICE_ID_APPLE_GEYSER4_HF_ISO

Set APPLE_ISO_KEYBOARD flag on USB_DEVICE_ID_APPLE_GEYSER4_HF_ISO so we get the ISO translation on German keyboards for the MacBook4,1 as well. Signed-off-by: Johannes Thumshirn --- drivers/hid/hid-apple.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/hid/hid-a

[PATCH 1/2] firmware loader: introduce module parameter to customize(v4) fw search path

This patch introduces one module parameter of 'path' in firmware_class to support customizing firmware image search path, so that people can use its own firmware path if the default built-in paths can't meet their demand[1], and the typical usage is passing the below from kernel command parameter w

[PATCH 2/2] firmware loader: document firmware cache mechanism

From: Ming Lei This patch documents the firmware cache mechanism so that users of request_firmware() know that it can be called safely inside device's suspend and resume callback, and the device's firmware needn't be cached any more by individual driver itself to deal with firmware loss during sy

[PATCH] atp: remove set_rx_mode_8012()

Building atp.o triggers this GCC warning: drivers/net/ethernet/realtek/atp.c: In function ‘set_rx_mode’: drivers/net/ethernet/realtek/atp.c:871:26: warning: ‘mc_filter[0]’ may be used uninitialized in this function [-Wuninitialized] GCC is correct. In promiscuous mode 'mc_filter' will be

Re: [REGRESSION] i915: failure to interoperate with HP ZR30w using an X230

On Fri, Nov 02, 2012 at 08:58:31PM -0400, Theodore Ts'o wrote: > Ping? > > On Tue, Oct 30, 2012 at 04:32:21PM -0400, Theodore Ts'o wrote: > > On Tue, Oct 30, 2012 at 01:57:27PM +0200, Jani Nikula wrote: > > > > [1] drm-intel-next-queued branch at > > > > git://people.freedesktop.org/~danvet/drm-i

Re: AMD A10: MCE Instruction Cache Error

Am 03.11.2012 05:49, schrieb Borislav Petkov: On Fri, Nov 02, 2012 at 02:53:45PM +0100, Alexander Holler wrote: Am 02.11.2012 11:50, schrieb Alexander Holler: Hello, I've just got the following on an AMD A10 5800K: -- [ 8395.999581] [Hardware Error]: CPU:0 MC1_STATUS[-|CE|MiscV|-|AddrV|-|

[PATCH 0/16] use WARN

These patches use WARN, which combines printk and WARN_ON(1), or WARN_ONCE, which combines printk and WARN_ON_ONCE(1). This does not appear to affect the behavior, but makes the code a little more concise. The semantic patch that makes this transformation is as follows (http://coccinelle.lip6.fr/

[PATCH 3/16] drivers/md/raid5.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 5/16] drivers/scsi: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 10/16] drivers/net/ethernet/ibm/emac/mal.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 11/16] drivers/misc/kgdbts.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 12/16] fs/logfs/gc.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 16/16] drivers/infiniband/hw/nes: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 15/16] drivers/parisc/pdc_stable.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 4/16] drivers/usb/wusbcore: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 14/16] drivers/ssb/main.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 13/16] fs/btrfs: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 9/16] fs/ext4/indirect.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 8/16] drivers/infiniband/hw/cxgb3/iwch_cm.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 7/16] drivers/scsi/gdth.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. If (count) is also merged into WARN, for further conciseness. A simplified version of the semantic patch that makes part of this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression

[PATCH 6/16] drivers/infiniband/hw/cxgb4/cm.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 2/16] fs/hfsplus/bnode.c: use WARN

From: Julia Lawall Use WARN rather than printk followed by WARN_ON(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN(1, es); -WARN_ON(1); // Signed-off-by:

[PATCH 1/16] drivers/gpu/drm/drm_cache.c: use WARN_ONCE

From: Julia Lawall Use WARN_ONCE rather than printk followed by WARN_ON_ONCE(1), for conciseness. A simplified version of the semantic patch that makes this transformation is as follows: (http://coccinelle.lip6.fr/) // @@ expression list es; @@ -printk( +WARN_ONCE(1, es); -WARN_ON_ONCE(1);

Re: [PATCH 00/31] numa/core patches

> > In reality, this report is larger but I chopped it down a bit for > brevity. autonuma beats schednuma *heavily* on this benchmark both in > terms of average operations per numa node and overall throughput. > > SPECJBB PEAKS >3.7.0 3.7

[GIT PULL] Thermal management & ACPI update for v3.7-rc4

Hi Linus, Could you please pull from the git repository at git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git release to receive three thermal and acpi fixes for v3.7-rc4. thanks, rui The following changes since commit 1e207eb1c3f0e8b690401f02fe08e7b53903f010: Merge git://git

Re: [PATCH 10/16] drivers/net/ethernet/ibm/emac/mal.c: use WARN

Am 03.11.2012 11:58, schrieb Julia Lawall: > From: Julia Lawall > > Use WARN rather than printk followed by WARN_ON(1), for conciseness. > > A simplified version of the semantic patch that makes this transformation > is as follows: (http://coccinelle.lip6.fr/) > > // > @@ > expression list e

Re: Fwd: Nice processes prevent frequency increases - possible scheduler regression (known good in 2.6.35)

On Fri, 2012-11-02 at 21:09 +0100, Michal Zatloukal wrote: > On the new kernel, the nice processes are never starved - even when > starting a tab-laden chromium session, the processes for BOINC keep > about 20% CPU each (that is normalized to all CPUs, ie 40% nice load > on each core). The problem

[git pull] drm fixes

Hi Linus, scattered selection of fixes: radeon: load detect fixes from SuSE/AMD intel: misc i830, sdvo regression, vesafb kickoff ums fix exynos: maintainers entry update + fixes udl: fix stride scanout issue its slightly bigger than I'd probably like, but nothing looked dangerous enough to hol

Re: [ 0/4] 3.0.51-stable review

On Fri, Nov 02, 2012 at 09:07:11PM -0700, Greg Kroah-Hartman wrote: > > > > Howdy Greg, > > > > Somehow the following patch is missing for this series submission: > > > Len Brown > > > x86: Remove the ancient and deprecated disable_hlt() and enable_hlt() > > > facility > > > > I glanced at

Re: Fwd: Nice processes prevent frequency increases - possible scheduler regression (known good in 2.6.35)

On Sat, 2012-11-03 at 04:33 -0700, Mike Galbraith wrote: > On Fri, 2012-11-02 at 21:09 +0100, Michal Zatloukal wrote: > > > On the new kernel, the nice processes are never starved - even when > > starting a tab-laden chromium session, the processes for BOINC keep > > about 20% CPU each (that is n

Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2

On 11/02/2012 09:43 AM, Pantelis Antoniou wrote: [...] And then use the standard DT support to create later the platform_device that does represent the new super-cape devices. We know this is the ideal case. In fact that's the long term goal and we had internal discussions about it. Sinc

Re: [PATCH v2] proc: add "Seccomp" to status

On Thu, Nov 01, 2012 at 11:35 -0700, Kees Cook wrote: > @@ -327,6 +327,13 @@ static inline void task_cap(struct seq_file *m, struct > task_struct *p) > render_cap_t(m, "CapBnd:\t", &cap_bset); > } > > +static inline void task_seccomp(struct seq_file *m, struct task_struct *p) > +{ > +#ifd

Re: [RFC] Second attempt at kernel secure boot support

On Sat, 2012-11-03 at 00:22 +, Matthew Garrett wrote: > On Fri, Nov 02, 2012 at 11:38:23PM +, James Bottomley wrote: > > On Fri, 2012-11-02 at 18:04 +, Matthew Garrett wrote: > > > A user runs a binary that elevates itself to admin. Absent any flaws in > > > Windows (cough), that shoul

Re: [PATCH v3 04/11] clk: davinci - add pll divider clock driver

On 11/2/2012 7:23 PM, Murali Karicheri wrote: > On 11/02/2012 07:33 AM, Sekhar Nori wrote: >> On 10/25/2012 9:41 PM, Murali Karicheri wrote: >> >>> pll dividers are present in the pll controller of DaVinci and Other >>> SoCs that re-uses the same hardware IP. This has a enable bit for >>> bypass th

Re: [PATCH v3 02/11] clk: davinci - add PSC clock driver

On 10/25/2012 9:41 PM, Murali Karicheri wrote: > This is the driver for the Power Sleep Controller (PSC) hardware > found on DM SoCs as well Keystone SoCs (c6x). This driver borrowed > code from arch/arm/mach-davinci/psc.c and implemented the driver > as per common clock provider API. The PSC modul

Re: [PATCH 11/16] drivers/misc/kgdbts.c: use WARN

Am 03.11.2012 11:58, schrieb Julia Lawall: > From: Julia Lawall > > Use WARN rather than printk followed by WARN_ON(1), for conciseness. > > A simplified version of the semantic patch that makes this transformation > is as follows: (http://coccinelle.lip6.fr/) > > // > @@ > expression list e

RE: [Xen-devel] [PATCH 1/2] Xen acpi pad implement

Konrad Rzeszutek Wilk wrote: >>> From f514b97628945cfac00efb0d456f133d44754c9d Mon Sep 17 00:00:00 >>> 2001 >> From: Liu, Jinsong >> Date: Thu, 1 Nov 2012 21:02:36 +0800 >> Subject: [PATCH 1/2] Xen acpi pad implement >> >> PAD is acpi Processor Aggregator Device which provides a control >> point

Re: [PATCH 00/31] numa/core patches

On Sat, Nov 03, 2012 at 07:04:04PM +0800, Alex Shi wrote: > > > > In reality, this report is larger but I chopped it down a bit for > > brevity. autonuma beats schednuma *heavily* on this benchmark both in > > terms of average operations per numa node and overall throughput. > > > > SPECJBB PEAKS >

Re: [PATCH v3 03/11] clk: davinci - common clk utilities to init clk driver

On 10/25/2012 9:41 PM, Murali Karicheri wrote: > This is the common clk driver initialization functions for DaVinci > SoCs and other SoCs that uses similar hardware architecture. > clock.h also defines struct types for clock definitions in a SoC > and clock data type for configuring clk-mux. The in

Re: [PATCH 8/16] drivers/infiniband/hw/cxgb3/iwch_cm.c: use WARN

Acked-by: Steve Wise -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 6/16] drivers/infiniband/hw/cxgb4/cm.c: use WARN

Acked-by: Steve Wise -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: setting up CDB filters in udev (was Re: [PATCH v2 0/3] block: add queue-private command filter, editable via sysfs)

Il 02/11/2012 18:53, Tejun Heo ha scritto: > Hello, Paolo. > > On Fri, Nov 02, 2012 at 06:49:43PM +0100, Paolo Bonzini wrote: >>> No rule is really absolute. To me, it seems the suggested in-kernel >>> per-device command code filter is both too big for the given problem >> >> Is it? 150 lines of

Re: [PATCH v3 05/11] clk: davinci - add dm644x clock initialization

On 10/25/2012 9:41 PM, Murali Karicheri wrote: > This patch adds dm644x clock initialization code that consists of > clocks data for various clocks and clock register callouts to > various clock drivers. It uses following clk drivers for this > > 1. clk-fixed-rate - for ref clock > 2. clk-mux -

[PATCH] staging/comedi: Use dev_ printks in drivers/adl_pci9118.c

fixed below checkpatch warnings. - WARNING: Prefer netdev_err(netdev, ... then dev_err(dev, ... then pr_err(... to printk(KERN_ERR ... Signed-off-by: YAMANE Toshiaki --- drivers/staging/comedi/drivers/adl_pci9118.c | 31 ++ 1 file changed, 17 insertions(+), 14 deletio

[PATCH] staging/comedi: fix the spaces issue around that '=' in drivers/ni_670x.c

fixed below checkpatch error. - ERROR: spaces required around that '=' (ctx:WxV) Signed-off-by: YAMANE Toshiaki --- drivers/staging/comedi/drivers/ni_670x.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/comedi/drivers/ni_670x.c b/drivers/staging/comedi/d

[PATCH] staging/comedi: Use dev_ printks in drivers/comedi_fc.c

fixed below checkpatch warning. - WARNING: Prefer netdev_warn(netdev, ... then dev_warn(dev, ... then pr_warn(... to printk(KERN_WARNING ... Signed-off-by: YAMANE Toshiaki --- drivers/staging/comedi/drivers/comedi_fc.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/driv

[PATCH] staging/comedi: fix the spaces issue around that '->' in drivers/gsc_hpdi.c

fixed below checkpatch error. - ERROR: spaces prohibited around that '->' (ctx:VxW) Signed-off-by: YAMANE Toshiaki --- drivers/staging/comedi/drivers/gsc_hpdi.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/comedi/drivers/gsc_hpdi.c b/drivers/staging/com

Re: [RFC] Second attempt at kernel secure boot support

On Sat, Nov 03, 2012 at 12:03:56PM +, James Bottomley wrote: > On Sat, 2012-11-03 at 00:22 +, Matthew Garrett wrote: > > Why would an attacker use one of those Linux systems? There's going to > > be plenty available that don't have that restriction. > > It's called best practices. If som

  1   2   3   >