[PATCH] staging: dgrp: fix potential NULL defereference issue

Fix a coccinelle warning catched by Fengguang's 0-DAY system: + drivers/staging/dgrp/dgrp_net_ops.c:1061:11-27: ERROR: nd is NULL but dereferenced. Put the "done:" label a bit down would solve this issue. Cc: Fengguang Wu Cc: Julia Lawall Cc: Greg Kroah-Hartman Signed-off-by: Yuanhan Liu

[PATCH v7 2/3] drivers/mmc: Add realtek pcie sdmmc host driver

From: Wei WANG Realtek PCI-E SD/MMC card host driver is used to access SD/MMC card, with the help of Realtek PCI-E card reader MFD driver. Signed-off-by: Wei WANG Reviewed-by: Arnd Bergmann Tested-by: Borislav Petkov --- drivers/mmc/host/Kconfig |7 + drivers/mmc/host/Makefile

[PATCH v7 3/3] drivers/memstick: Add realtek pcie memstick host driver

From: Wei WANG Realtek PCI-E Memstick card host driver is used to access Memstick card, with the help of Realtek PCI-E card reader MFD driver. Signed-off-by: Wei WANG Acked-by: Alex Dubov --- drivers/memstick/host/Kconfig | 10 + drivers/memstick/host/Makefile |1 +

[PATCH v7 0/3] Add modules to support realtek PCIE card reader

From: Wei WANG Support for Realtek PCI-Express driver-based card readers including rts5209, rts5229 and rtl8411. v2: 1. Using platform device to replace realtek slot bus v3: 1. Fix a bug that DMA out of SW-IOMMU space in Lenovo Thinkpad x121e 2. Tested by Borislav Petkov v4: 1. Fulfill power

[net-next v4 1/7] tuntap: log the unsigned informaiton with %u

Signed-off-by: Jason Wang --- drivers/net/tun.c |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/net/tun.c b/drivers/net/tun.c index 0873cdc..ef13cf0 100644 --- a/drivers/net/tun.c +++ b/drivers/net/tun.c @@ -1422,7 +1422,7 @@ static long

Re: Re: Re: [Pv-drivers] 3.7-rc2 regression : file copied to CIFS-mounted directory corrupted

--- Original Message --- Sender : Jongman Heo Date : 2012-10-24 11:53 (GMT+09:00) Title : Re: Re: [Pv-drivers] 3.7-rc2 regression : file copied to CIFS-mounted directory corrupted Hi, --- Original Message --- Sender : Eric Dumazet Date : 2012-10-24 04:39 (GMT+09:00) Title :

[net-next v4 7/7] tuntap: choose the txq based on rxq

This patch implements a simple multiqueue flow steering policy - tx follows rx for tun/tap. The idea is simple, it just choose the txq based on which rxq it comes. The flow were identified through the rxhash of a skb, and the hash to queue mapping were recorded in a hlist with an ageing timer to

[net-next v4 6/7] tuntap: add ioctl to attach or detach a file form tuntap device

Sometimes usespace may need to active/deactive a queue, this could be done by detaching and attaching a file from tuntap device. This patch introduces a new ioctls - TUNSETQUEUE which could be used to do this. Flag IFF_ATTACH_QUEUE were introduced to do attaching while IFF_DETACH_QUEUE were

[net-next v4 5/7] tuntap: multiqueue support

This patch converts tun/tap to a multiqueue devices and expose the multiqueue queues as multiple file descriptors to userspace. Internally, each tun_file were abstracted as a queue, and an array of pointers to tun_file structurs were stored in tun_structure device, so multiple tun_files were

[net-next v4 4/7] tuntap: introduce multiqueue flags

Add flags to be used by creating multiqueue tuntap device. Signed-off-by: Jason Wang --- include/uapi/linux/if_tun.h |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/include/uapi/linux/if_tun.h b/include/uapi/linux/if_tun.h index 25a585c..8ef3a87 100644 ---

[net-next v4 3/7] tuntap: RCUify dereferencing between tun_struct and tun_file

RCU were introduced in this patch to synchronize the dereferences between tun_struct and tun_file. All tun_{get|put} were replaced with RCU, the dereference from one to other must be done under rtnl lock or rcu read critical region. This is needed for the following patches since the one of the

[net-next v4 2/7] tuntap: move socket to tun_file

Current tuntap makes use of the socket receive queue as its tx queue. To implement multiple tx queues for tuntap and enable the ability of adding and removing queues during workload, the first step is to move the socket related structures to tun_file. Then we could let multiple fds/sockets to be

[PATCH] tuntap: choose the txq based on rxq

This patch implements a simple multiqueue flow steering policy - tx follows rx for tun/tap. The idea is simple, it just choose the txq based on which rxq it comes. The flow were identified through the rxhash of a skb, and the hash to queue mapping were recorded in a hlist with an ageing timer to

[net-next v4 0/7] Multiqueue support in tuntap

Hello All: This is an update of multiqueue support in tuntap from V3. Please consider to merge. The main idea for this series is to let tun/tap device to be benefited from multiqueue network cards and multi-core host. We used to have a single queue for tuntap which could be a bottleneck in a

Re: [PATCH 6/9] uprobes: flush cache after xol write

On Fri, Oct 26, 2012 at 06:39:51PM +0200, Oleg Nesterov wrote: > On 10/26, Ananth N Mavinakayanahalli wrote: > > > > On Thu, Oct 25, 2012 at 04:58:39PM +0200, Oleg Nesterov wrote: > > > On 10/16, Rabin Vincent wrote: > > > > > > > > >> --- a/kernel/events/uprobes.c > > > > >> +++

Re: [PATCH 2/4] uprobes/powerpc: Do not use arch_uprobe_*_step() helpers

On Sun, Oct 28, 2012 at 06:39:28PM +0100, Oleg Nesterov wrote: > No functional changes. > > powerpc is the only user of arch_uprobe_enable/disable_step() helpers, > but they should die. They can not be used correctly, every arch needs > its own implementation (like x86 does). And they do not

Re: [PATCH 1/4] uprobes/powerpc: Don't clear TIF_UPROBE in do_notify_resume()

On Sun, Oct 28, 2012 at 06:39:25PM +0100, Oleg Nesterov wrote: Hi Oleg, > Cleanup. No need to clear TIF_UPROBE, do_notify_resume() does this. > > Signed-off-by: Oleg Nesterov > --- > arch/powerpc/kernel/signal.c |4 +--- > 1 files changed, 1 insertions(+), 3 deletions(-) > > diff --git

[PATCH RFT] leds: blinkm: Don't init a workqueue per brightness_set call

Calling INIT_WORK in blinkm_led_common_set() means we init a workqueue every time when brightness_set callback is called. Move INIT_WORK to blinkm_probe() so we only need to init the workqueue once. So we only need to init a workqueue per blinkm led rather than init a workqueue per

Re: [PATCH] async_tx: use memchr_inv

On Sun, 2012-10-28 at 00:49 +0900, Akinobu Mita wrote: > Use memchr_inv() to check the specified page is filled with zero. > > Signed-off-by: Akinobu Mita > Cc: Vinod Koul > Cc: Dan Williams > --- Looks fine to me, need Dan;s ack before applying > crypto/async_tx/async_xor.c | 4 +--- > 1

Re: [PATCH v2 3/4] DMA: PL330: Balance module remove function with probe

On Sat, 2012-10-27 at 15:50 +0530, Inderpal Singh wrote: > Hi Vinod, > > On 26 October 2012 10:15, Vinod Koul wrote: > > On Thu, 2012-10-25 at 16:53 +0530, Inderpal Singh wrote: > >> > >> This code will get executed only in case of force removal of the > >> module which was discussed in the

[PATCH 2/2] backlight: max8925: drop devm_kfree of devm_kzalloc'd data

The devm_kfree function allocates memory that is released when a driver detaches. Thus, there is no reason to explicitly call devm_kfree in probe or remove functions. Signed-off-by: Jingoo Han Cc: Richard Purdie --- drivers/video/backlight/max8925_bl.c | 11 +++ 1 files changed, 3

[PATCH 1/2] backlight: 88pm860x: drop devm_kfree of devm_kzalloc'd data

The devm_kfree function allocates memory that is released when a driver detaches. Thus, there is no reason to explicitly call devm_kfree in probe or remove functions. Signed-off-by: Jingoo Han Cc: Richard Purdie --- drivers/video/backlight/88pm860x_bl.c | 11 +++ 1 files changed, 3

[RFC v4+ hot_track 01/19] vfs: introduce private radix tree structures

From: Zhi Yong Wu One root structure hot_info is defined, is hooked up in super_block, and will be used to hold radix tree root, hash list root and some other information, etc. Adds hot_inode_tree struct to keep track of frequently accessed files, and be keyed by {inode, offset}. Trees

[RFC v4+ hot_track 05/19] vfs: add hooks to enable hot tracking

From: Zhi Yong Wu Miscellaneous features that implement hot data tracking and generally make the hot data functions a bit more friendly. Signed-off-by: Zhi Yong Wu --- fs/direct-io.c |6 ++ mm/filemap.c|6 ++ mm/page-writeback.c | 12

[RFC v4+ hot_track 08/19] vfs: add aging function

From: Zhi Yong Wu Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c | 56 + fs/hot_tracking.h |6 + 2 files changed, 62 insertions(+), 0 deletions(-) diff --git a/fs/hot_tracking.c b/fs/hot_tracking.c index 9245dd3..fff0038 100644

[RFC v4+ hot_track 09/19] vfs: add one work queue

From: Zhi Yong Wu Add a per-superblock workqueue and a delayed_work to run periodic work to update map info on each superblock. Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c| 85 ++ fs/hot_tracking.h|3 +

[RFC v4+ hot_track 14/19] vfs: add debugfs support

From: Zhi Yong Wu Add a /sys/kernel/debug/hot_track// directory for each volume that contains two files. The first, `inode_stats', contains the heat information for inodes that have been brought into the hot data map structures. The second, `range_stats', contains similar information for

[RFC v4+ hot_track 17/19] xfs: add hot tracking support

From: Dave Chinner Connect up the VFS hot tracking support so XFS filesystems can make use of it. Signed-off-by: Dave Chinner --- fs/xfs/xfs_mount.h |1 + fs/xfs/xfs_super.c | 16 2 files changed, 17 insertions(+), 0 deletions(-) diff --git a/fs/xfs/xfs_mount.h

[RFC v4+ hot_track 15/19] sysfs: add two hot_track proc files

From: Zhi Yong Wu Add two proc files hot-kick-time and hot-update-delay under the dir /proc/sys/fs/ in order to turn TIME_TO_KICK and HEAT_UPDATE_DELAY into be tunable. Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c| 12 +--- fs/hot_tracking.h|9

[RFC v4+ hot_track 11/19] vfs: register one shrinker

From: Zhi Yong Wu Register a shrinker to control the amount of memory that is used in tracking hot regions - if we are throwing inodes out of memory due to memory pressure, we most definitely are going to need to reduce the amount of memory the tracking code is using, even if it means losing

[RFC v4+ hot_track 19/19] vfs: add documentation

From: Zhi Yong Wu Add one doc for VFS hot tracking feature Signed-off-by: Zhi Yong Wu --- Documentation/filesystems/00-INDEX |2 + Documentation/filesystems/hot_tracking.txt | 262 2 files changed, 264 insertions(+), 0 deletions(-) create mode

[RFC v4+ hot_track 13/19] debugfs: introduce one function

From: Zhi Yong Wu The debugfs function is used to get expected dentry. Signed-off-by: Zhi Yong Wu --- fs/debugfs/inode.c | 26 ++ include/linux/debugfs.h |9 + 2 files changed, 35 insertions(+), 0 deletions(-) diff --git a/fs/debugfs/inode.c

[RFC v4+ hot_track 18/19] ext4: add hot tracking support

From: Zheng Liu Define a new mount option to add VFS hot tracking support in order to use it in ext4. CC: Zhi Yong Wu Signed-off-by: Zheng Liu --- fs/ext4/ext4.h |3 +++ fs/ext4/super.c | 13 - 2 files changed, 15 insertions(+), 1 deletions(-) diff --git

[RFC v4+ hot_track 16/19] btrfs: add hot tracking support

From: Zhi Yong Wu Introduce one new mount option '-o hot_track', and add its parsing support. Its usage looks like: mount -o hot_track mount -o nouser,hot_track mount -o nouser,hot_track,loop mount -o hot_track,nouser Signed-off-by: Zhi Yong Wu --- fs/btrfs/ctree.h |1 +

[RFC v4+ hot_track 12/19] vfs: add one ioctl interface

From: Zhi Yong Wu FS_IOC_GET_HEAT_INFO: return a struct containing the various metrics collected in hot_freq_data structs, and also return a calculated data temperature based on those metrics. Optionally, retrieve the temperature from the hot data hash list instead of recalculating it.

[RFC v4+ hot_track 10/19] vfs: introduce hot func register framework

From: Zhi Yong Wu Introduce one framwork to enable that specific FS can register its own hot tracking functions. Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c| 78 ++ include/linux/hot_tracking.h | 25 + 2 files changed,

[RFC v4+ hot_track 06/19] vfs: add temp calculation function

From: Zhi Yong Wu Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c | 74 + 1 files changed, 74 insertions(+), 0 deletions(-) diff --git a/fs/hot_tracking.c b/fs/hot_tracking.c index 0a603a1..83e590c 100644 --- a/fs/hot_tracking.c +++

[RFC v4+ hot_track 07/19] vfs: add map info update function

From: Zhi Yong Wu Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c | 66 + fs/hot_tracking.h | 21 + 2 files changed, 87 insertions(+), 0 deletions(-) diff --git a/fs/hot_tracking.c b/fs/hot_tracking.c index

[RFC v4+ hot_track 04/19] vfs: add two map arrays

From: Zhi Yong Wu Adds two map arrays which contains a lot of list and is used to efficiently look up the data temperature of a file or its ranges. In each list of map arrays, the array node will keep track of temperature info. Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c|

[RFC v4+ hot_track 03/19] vfs: add I/O frequency update function

From: Zhi Yong Wu Add some util helpers to update access frequencies for one file or its range. Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c| 179 ++ fs/hot_tracking.h|7 ++ include/linux/hot_tracking.h |2 + 3

[RFC v4+ hot_track 02/19] vfs: initialize and free data structures

From: Zhi Yong Wu Add initialization function to create some key data structures when hot tracking is enabled; Clean up them when hot tracking is disabled Signed-off-by: Zhi Yong Wu --- fs/hot_tracking.c| 124 ++ fs/hot_tracking.h

[RFC v4+ hot_track 00/19] vfs: hot data tracking

From: Zhi Yong Wu NOTE: The patchset can be obtained via my kernel dev git on github: g...@github.com:wuzhy/kernel.git hot_tracking If you're interested, you can also can review them via https://github.com/wuzhy/kernel/commits/hot_tracking For more info, please check hot_tracking.txt in

Re: linux-next: Tree for Oct 29 (tty->raw)

On 10/28/2012 08:46 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20121026: > Who made some changes that remove tty->raw ? There is still one occurrence in arch/um that is causing a build error (on x86_64 defconfig): arch/um/drivers/chan_kern.c: In function 'tty_receive_char':

Regression from 3.4.9 to 3.4.16 "stable" kernel

My server here runs the 3.4.xx series of "stable" kernels. Until today, it was running 3.4.9. Today I tried to upgrade it to 3.4.16. It hangs in setup.c. I've isolated the fault down to this specific change that was made between 3.4.9 and 3.4.16. Reverting this change allows the system to

[PATCH v5 3/8] perf ui/browser: Add a browser for perf script

Create a script browser, so that user can check all the available scripts for current perf data file and run them inside the main perf report or annotation browsers, for all perf samples or for samples belong to one thread/symbol. Please be noted: current script browser is only for report use,

[PATCH v5 4/8] perf ui/browser: Integrate script browser into annotation browser

Integrate the script browser into annotation, users can press function key 'r' to list all perf scripts and select one of them to run that script, the output will be shown in a separate browser. Signed-off-by: Feng Tang --- tools/perf/ui/browsers/annotate.c |6 ++ 1 file changed, 6

[PATCH v5 5/8] perf ui/browser: Integrate script browser into main hists browser

Integrate the script browser into "perf report" framework, users can use function key 'r' or the drop down menu to list all perf scripts and select one of them, just like they did for the annotation. Signed-off-by: Feng Tang --- tools/perf/ui/browsers/hists.c | 38

[PATCH v5 7/8] perf hists browser: Add option for runtime switching perf data file

Based on perf report/top/scripts browser integration idea from acme. This will enable user to runtime switch the data file, when this option is selected, it will popup all the legal data files in current working directory, and the filename selected by user is saved in the global variable

[PATCH v5 1/8] perf tool: Add a global variable "const char *input_name"

Currently many perf commands annotate/evlist/report/script/lock etc all support "-i" option to chose a specific perf data, and all of them create a local "input_name" to save the file name for that perf data. Since most of these commands need it, we can add a global variable for it, also it can

[PATCH v5 2/8] perf script: Add more filter to find_scripts()

As suggested by Arnaldo, many scripts have their own usages and need capture specific events or tracepoints, so only those scripts whose target events match the events in current perf data file should be listed in the script browser menu. This patch will add the event match checking, by opening

[PATCH v5 8/8] perf report: Enable the runtime switching of perf data file

This is for tui browser only. This patch will check the returned key of tui hists browser, if it's K_SWITH_INPUT_DATA, then recreate a session for the new selected data file. Signed-off-by: Feng Tang --- tools/perf/builtin-report.c | 18 -- 1 file changed, 16 insertions(+), 2

[PATCH v5 6/8] perf header: Add is_perf_magic() func

With this function, other modules can basically check whether a file is a legal perf data file by checking its first 8 bytes against all possible perf magic numbers. Change the function name from check_perf_magic to more meaningful is_perf_magic as suggested by acme. Signed-off-by: Feng Tang

[PATCH v5 0/8] perf tools: Add script browser and runtime data file switch

Hi Arnaldo and all, This patch set make 2 changes to perf tool: 1. Add a browser for perf script, which will be integrated into the main hists and annotation browser. 2. Add the inital support for runtime perf data file switch in the 'perf report' window. Patch 1Add the global variable

linux-next: Tree for Oct 29

Hi all, Changes since 20121026: New tree: bcm2835 The v4l-dvb tree gained a build failure so I used the version from next-20121026. The sound-asoc tree gained a build failure so I used the version from next-20121026. The signal tree gained a conflict against the sparc tree. The akpm tree

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

It's doable to register a stub for xen. However, it's not preferred, say, to make xen pad as module, considering the case 'rmmod xen_acpi_pad' then 'insmod acpi_pad'? Under such case there is risk of mwait #UD, if we want to remove mwait check as 'patch 2/2:

Re: [PATCH -v3] ext4: fix unjournaled inode bitmap modification

On 10/28/12 9:30 PM, Theodore Ts'o wrote: > On Sat, Oct 27, 2012 at 11:23:57PM -0500, Eric Sandeen wrote: >> A little more going on here to try to properly handle error >> cases & moving to the next group; despite >> ext4_handle_release_buffer being a no-op, I've tried >> to sprinkle it in at the

linux-next: manual merge of the akpm-current tree with the staging tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in drivers/staging/rts_pstor/trace.h between commit cd2112220b6b ("Staging: remove rts_pstor driver") from the staging tree and commit 3980a6d4af3e ("staging: rts_pstor: use kbasename()") from the akpm-current tree. The

[GIT PULL REQUEST] UniCore32 update for v3.7-rc2

The following changes since commit e657e078d3dfa9f96976db7a2b5fd7d7c9f1f1a6: Linus Torvalds (1): Merge git://git.kernel.org/.../davem/net are available in the git repository at: git://github.com/gxt/linux.git unicore32 Al Viro (2): unicore32: switch to generic

[PATCH v3] Do not change worker's running cpu in cmci_rediscover().

cmci_rediscover() used set_cpus_allowed_ptr() to change the current process's running cpu, and migrate itself to the dest cpu. But worker processes are not allowed to be migrated. If current is a worker, the worker will be migrated to another cpu, but the corresponding worker_pool is still on the

Re: linux-next: manual merge of the signal tree with the sparc tree

From: Stephen Rothwell Date: Mon, 29 Oct 2012 14:00:32 +1100 > Today's linux-next merge of the signal tree got a conflict in > arch/sparc/kernel/sys_sparc_64.c between commit 517ffce4e1a0 ("sparc64: > Make montmul/montsqr/mpmul usable in 32-bit threads") from the sparc tree > and commit

linux-next: manual merge of the signal tree with the sparc tree

Hi Al, Today's linux-next merge of the signal tree got a conflict in arch/sparc/kernel/sys_sparc_64.c between commit 517ffce4e1a0 ("sparc64: Make montmul/montsqr/mpmul usable in 32-bit threads") from the sparc tree and commit 2f12af35a988 ("sparc64: switch to generic kernel_execve()") from the

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

On 10/29/2012 01:56 AM, Johannes Weiner wrote: On Fri, Oct 26, 2012 at 11:08:00AM +0200, Peter Zijlstra wrote: On Fri, 2012-10-26 at 17:07 +0800, Zhouping Liu wrote: [ 180.918591] RIP: 0010:[] [] mem_cgroup_prepare_migration+0xba/0xd0 [ 182.681450] [] do_huge_pmd_numa_page+0x180/0x500 [

Re: [PATCH] V2 sched, autogroup: fix crash on reboot when autogroup is disabled

On Mon, Oct 29, 2012 at 3:19 AM, Mike Galbraith wrote: > On Sun, 2012-10-28 at 15:05 +0100, Ingo Molnar wrote: >> * Mike Galbraith wrote: >> >> > On Sun, 2012-10-28 at 14:19 +0100, Ingo Molnar wrote: >> > > * Mike Galbraith wrote: >> > > >> > > > On Sun, 2012-10-28 at 11:25 +0100, Ingo Molnar

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On Sun, Oct 28, 2012 at 09:35:58PM -0500, Eric Sandeen wrote: > Yeah, seems that way. > > Then your simpler version is probably the way to go. If you have a chance, could you do me a favor and test my -v3 version of the patch? It should work just as well as yours, but I'm getting paranoid in my

Re: [PATCH 030/193] arch/unicore32: remove CONFIG_EXPERIMENTAL

> This config item has not carried much meaning for a while now and is > almost always enabled by default. As agreed during the Linux kernel > summit, remove it. > > CC: Guan Xuetao > Signed-off-by: Kees Cook Thanks. I will push it in my tree. Acked-by: Guan Xuetao > --- >

Re: [PATCH 2/3] ext4: introduce ext4_error_remove_page

On Mon, Oct 29, 2012 at 12:16:32PM +1100, Dave Chinner wrote: > > Except that there are filesystems that cannot implement such flags, > or require on-disk format changes to add more of those flags. This > is most definitely not a filesystem specific behaviour, so any sort > of VFS level per-file

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 10/28/12 9:34 PM, Theodore Ts'o wrote: > On Sun, Oct 28, 2012 at 09:24:19PM -0500, Eric Sandeen wrote: >> Yeah, I knew it wasn't ;) I did resend >> [PATCH] ext4: fix unjournaled inode bitmap modification >> which is a bit more involved. > > Yeah, sorry, I didn't see your updated patch at

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On Sun, Oct 28, 2012 at 09:24:19PM -0500, Eric Sandeen wrote: > Yeah, I knew it wasn't ;) I did resend > [PATCH] ext4: fix unjournaled inode bitmap modification > which is a bit more involved. Yeah, sorry, I didn't see your updated patch at first, since this mail thread is one complicated

[PATCH] Sometimes, there is OOPS happened when we use oprofile.

>From fff479313342940372444797814edee996b18fc9 Mon Sep 17 00:00:00 2001 From: jzha144 Date: Mon, 29 Oct 2012 09:07:22 +0800 Subject: [PATCH] Sometimes, there is OOPS happened when we use oprofile. next is the call stack. From call stack, we find in call_on_stack if there is a nmi interrupt

[PATCH -v3] ext4: fix unjournaled inode bitmap modification

On Sat, Oct 27, 2012 at 11:23:57PM -0500, Eric Sandeen wrote: > A little more going on here to try to properly handle error > cases & moving to the next group; despite > ext4_handle_release_buffer being a no-op, I've tried > to sprinkle it in at the right places. Double checking > on review is

iwlwifi crash with queue full and qos errors

Reporting a possible regression with latest kernel 3.6.2-1. Intel's iwlwifi crashes intermittently. Downgraded to 3.5.3.1 including the microcode drivers and didnot notice any crashes since. Chunks from stack trace: [108759.658475] iwlwifi :03:00.0: fail to flush all tx fifo queues

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 10/28/12 8:00 PM, Theodore Ts'o wrote: > On Sat, Oct 27, 2012 at 05:42:07PM -0500, Eric Sandeen wrote: >> >> It looks like the inode_bitmap_bh is being modified outside a transaction: >> >> ret2 = ext4_test_and_set_bit(ino, inode_bitmap_bh->b_data); >> >> It needs a

Re: [RFC v4 03/15] vfs,hot_track: add the function for collecting I/O frequency

On Mon, Oct 29, 2012 at 10:01 AM, Dave Chinner wrote: > On Sun, Oct 28, 2012 at 09:51:48PM +0800, Zhi Yong Wu wrote: >> On Sun, Oct 28, 2012 at 3:55 PM, Zheng Liu wrote: >> > Hi Zhiyong, >> > >> > On Thu, Oct 25, 2012 at 11:08:55PM +0800, zwu.ker...@gmail.com wrote: >> > [snip] >> >> @@ -199,6

[PATCH] hrtimer: Printing timer info when hitting BUG_ON()

We encounted one BUG_ON() issue at function __run_hrtimer(), but the panic info is not enough to find out which hrtimer users use the hrtimer wrongly. (in this BUG_ON case, it is callback running at the same time hrtimer_start() is executed on different context.) We can print basic timer info

Re: [PATCH 0/5] minor clean-up and optimize highmem related code

Hi Joonsoo, On Mon, Oct 29, 2012 at 04:12:51AM +0900, Joonsoo Kim wrote: > This patchset clean-up and optimize highmem related code. > > [1] is just clean-up and doesn't introduce any functional change. > [2-3] are for clean-up and optimization. > These eliminate an useless lock opearation and

Re: [PATCH 5/5] mm, highmem: get virtual address of the page using PKMAP_ADDR()

On Mon, Oct 29, 2012 at 04:12:56AM +0900, Joonsoo Kim wrote: > In flush_all_zero_pkmaps(), we have an index of the pkmap associated the page. > Using this index, we can simply get virtual address of the page. > So change it. > > Signed-off-by: Joonsoo Kim Reviewed-by: Minchan Kim -- Kind

Re: [RFC v4 03/15] vfs,hot_track: add the function for collecting I/O frequency

On Sun, Oct 28, 2012 at 09:51:48PM +0800, Zhi Yong Wu wrote: > On Sun, Oct 28, 2012 at 3:55 PM, Zheng Liu wrote: > > Hi Zhiyong, > > > > On Thu, Oct 25, 2012 at 11:08:55PM +0800, zwu.ker...@gmail.com wrote: > > [snip] > >> @@ -199,6 +342,54 @@ err: > >> } > >> > >> /* > >> + * Main function to

Re: [PATCH 4/5] mm, highmem: makes flush_all_zero_pkmaps() return index of last flushed entry

On Mon, Oct 29, 2012 at 04:12:55AM +0900, Joonsoo Kim wrote: > In current code, after flush_all_zero_pkmaps() is invoked, > then re-iterate all pkmaps. It can be optimized if flush_all_zero_pkmaps() > return index of flushed entry. With this index, > we can immediately map highmem page to virtual

Re: [PATCH 3/5] mm, highmem: remove page_address_pool list

On Mon, Oct 29, 2012 at 04:12:54AM +0900, Joonsoo Kim wrote: > We can find free page_address_map instance without the page_address_pool. > So remove it. > > Signed-off-by: Joonsoo Kim Reviewed-by: Minchan Kim See below a nitpick. :) > > diff --git a/mm/highmem.c b/mm/highmem.c > index

Re: [BUG] perf parser: does not support arbitrary new sysfs events

Stephane Eranian writes: > Hi, > > The latest round of perf parser changes broke my PEBS-LL patch series > (at the last minute). For PEBS-LL, I need to add to generic events but I want > to keep them PMU specific. As such, they need to live in the sysfs events > subdir:

Re: [PATCH 2/5] mm, highmem: remove useless pool_lock

On Mon, Oct 29, 2012 at 04:12:53AM +0900, Joonsoo Kim wrote: > The pool_lock protects the page_address_pool from concurrent access. > But, access to the page_address_pool is already protected by kmap_lock. > So remove it. > > Signed-off-by: Joonsoo Kim Reviewed-by: Minchan Kin Looks good to

Re: [PATCH 1/5] mm, highmem: use PKMAP_NR() to calculate an index of pkmap

On Mon, Oct 29, 2012 at 04:12:52AM +0900, Joonsoo Kim wrote: > To calculate an index of pkmap, using PKMAP_NR() is more understandable > and maintainable, So change it. > > Cc: Mel Gorman > Signed-off-by: Joonsoo Kim Reviewed-by: Minchan Kim -- Kind regards, Minchan Kim -- To unsubscribe

Re: [PATCH v7 08/16] block,elevator: use new hashtable implementation

On Sun, Oct 28, 2012 at 03:02:20PM -0400, Sasha Levin wrote: > Switch elevator to use the new hashtable implementation. This reduces the > amount of > generic unrelated code in the elevator. > > This also removes the dymanic allocation of the hash table. The size of the > table is > constant so

Re: [PATCH v7 04/16] workqueue: use new hashtable implementation

On Sun, Oct 28, 2012 at 03:02:16PM -0400, Sasha Levin wrote: > Switch workqueues to use the new hashtable implementation. This reduces the > amount of > generic unrelated code in the workqueues. > > Signed-off-by: Sasha Levin Acked-by: Tejun Heo Thanks! -- tejun -- To unsubscribe from this

Re: [PATCH 2/3] ext4: introduce ext4_error_remove_page

On Sat, Oct 27, 2012 at 06:16:26PM -0400, Theodore Ts'o wrote: > On Fri, Oct 26, 2012 at 10:24:23PM +, Luck, Tony wrote: > > > Well, we could set a new attribute bit on the file which indicates > > > that the file has been corrupted, and this could cause any attempts to > > > open the file to

Re: [PATCH] cpuidle: add missing header include

On Monday, October 29, 2012 6:49 AM Marek Vasut wrote > > On 10/26/2012 06:30 AM, Jingoo Han wrote: > > This patch adds missing device.h header to fix build warnings as below: > > > > drivers/cpuidle/cpuidle.h:26:41: warning: 'struct device' declared inside > > parameter list [enabled by >

Re: [PATCH] asm-generic/io.h: remove asm/cacheflush.h include

> Including from prevents > cacheflush.h being able to use I/O functions like readl and writel due > to circular include dependencies. It doesn't appear as if anything from > cacheflush.h is actually used by the generic io.h, so remove the > include. > > I've compile tested a defconfig

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On 29 Oct 2012, Theodore Ts'o spake thusly: > commit 119c0d4460b001e44b41dcf73dc6ee794b98bd31 modified this function > such that the inode bitmap was being modified outside a transaction, > which could lead to corruption, and was discovered when journal_checksum > found a bad

Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?)

On Sat, Oct 27, 2012 at 05:42:07PM -0500, Eric Sandeen wrote: > > It looks like the inode_bitmap_bh is being modified outside a transaction: > > ret2 = ext4_test_and_set_bit(ino, inode_bitmap_bh->b_data); > > It needs a get_write_access / handle_dirty_metadata pair around it.

Re: [PATCH v2] Remove uninitialized_var()

On 28/10/12 21:20, Ingo Molnar wrote: > > * Andrew Morton wrote: > >> On Sat, 27 Oct 2012 15:12:03 +0200 Ingo Molnar wrote: >> >>> There's 3 types of conversions done: >>> >>>uninitialized_var(x)=> x = 0 /* for scalar types */ >>>uninitialized_var(x)=> x = NULL

[PATCH] netfilter: ipv6: use PTR_RET

Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR Generated by: coccinelle/api/ptr_ret.cocci Signed-off-by: Fengguang Wu --- net/ipv6/netfilter/ip6table_nat.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) --- linux-next.orig/net/ipv6/netfilter/ip6table_nat.c 2012-10-23

linux-next: build failure after merge of the sound-asoc tree

Hi all, After merging the sound-asoc tree, today's linux-next build (x86_64 allmodconfig) failed like this: make[4]: *** No rule to make target `sound/soc/codecs/snd-soc-wm-adsp.c', needed by `sound/soc/codecs/snd-soc-wm-adsp.o'. Stop. Caused by commit 2882fcb3cfe6 ("ASoC: adsp: Add ADSP base

[PATCH] netfilter: use PTR_RET

Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR Generated by: coccinelle/api/ptr_ret.cocci Reported-by: Fengguang Wu --- net/ipv4/netfilter/iptable_nat.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) --- linux-next.orig/net/ipv4/netfilter/iptable_nat.c2012-10-23

Re: [PATCH] r8169: Fix WoL on RTL8168d/8111d.

Francois Romieu (29/10/2012): > Cyril Brulebois : > > This regression was spotted between Debian squeeze and Debian wheezy > > kernels (respectively based on 2.6.32 and 3.2). The fix was inspired > > by , using > > RTL_GIGA_MAC_VER_{25,26} for

Re: [PATCH v4 0/5] zynq subarch cleanups

On Sun, Oct 28, 2012 at 05:26:05PM -0600, Josh Cartwright wrote: > Michal- Ugh, sorry everyone, I fatfingered the subject line. This is indeed v5. Josh pgpQ4dxD3axJl.pgp Description: PGP signature

linux-next: build failure after merge of the v4l-dvb tree

Hi Mauro, After merging the v4l-dvb tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/hid/hid-picolcd_cir.c: In function 'picolcd_init_cir': drivers/hid/hid-picolcd_cir.c:119:27: error: 'RC_TYPE_ALL' undeclared (first use in this function) Caused by commit

[PATCH v4 5/5] zynq: move static peripheral mappings

Shifting them up into the vmalloc region prevents the following warning, when booting a zynq qemu target with more than 512mb of RAM: BUG: mapping for 0xe000 at 0xe000 out of vmalloc space In addition, it allows for reuse of these mappings when the proper drivers issue requests via

[PATCH v4 0/5] zynq subarch cleanups

Michal- Here is a v5 of the zynq cleanup patchset that addresses your feedback. I've intentionally left patches 4 and 5 in the set until we figure out the appropriate way to get them in tree (feel free to just apply 1-3) I've also moved the uart mapping in patch 5 to a known working address,

[PATCH v4 2/5] zynq: use pl310 device tree bindings

The Zynq has a PL310 L2 cache controller. Convert in-tree uses to using the device tree. Signed-off-by: Josh Cartwright Cc: John Linn Acked-by: Arnd Bergmann Acked-by: Michal Simek --- arch/arm/boot/dts/zynq-ep107.dts | 9 + arch/arm/mach-zynq/common.c| 9

[PATCH v4 3/5] zynq: remove use of CLKDEV_LOOKUP

The Zynq support in mainline does not (yet) make use of any of the generic clk or clk lookup functionality. Remove what is upstream for now, until the out-of-tree implementation is in suitable form for merging. An important side effect of this patch is that it allows the building of a Zynq

  1   2   3   4   5   6   7   8   9   >