ffsb job does not exit on xfs 4.14-rc1+

2017-09-24 Thread Xiong Zhou
Hi, ffsb test won't exit like this on Linus tree 4.14-rc1+. Latest commit cd4175b11685 This does not happen on v4.13 Thanks, 1 1505 Ss 0 0:00 /usr/sbin/sshd -D 1505 1752 Ss 0 0:00 \_ sshd: root [priv] 1752 1762 S0 0:00 | \_ sshd: root@pts/0 1762 1763 Ss 0 0:

Re: fanotify_mark FAN_MARK_FLUSH | _MOUNT stress blocks write to directory

2017-08-30 Thread Xiong Zhou
On Thu, Aug 31, 2017 at 07:52:41AM +0300, Amir Goldstein wrote: > On Thu, Aug 31, 2017 at 6:51 AM, Xiong Zhou wrote: > > hi, > > > > This happens on 4.13.0-rc7+ to commit 42ff72c > > Don't understand. Is this a regression? from which commit? No. I'm just s

fanotify_mark FAN_MARK_FLUSH | _MOUNT stress blocks write to directory

2017-08-30 Thread Xiong Zhou
hi, This happens on 4.13.0-rc7+ to commit 42ff72c After firing up the stress, touch a file in monitoring directory could hang like forever. Pretty easy to hit. Thanks, Xiong [ 492.060879] INFO: task touch:2259 blocked for more than 120 seconds. [ 492.093497] Not tainted 4.13.0-rc7-mast

0324 tree BUG at kernel/auditsc.c:1513!

2017-03-24 Thread Xiong Zhou
[11230.930568] [ cut here ] [11230.953828] kernel BUG at kernel/auditsc.c:1513! [11230.976157] invalid opcode: [#1] SMP [11230.995917] Modules linked in: btrfs xor raid6_pq ext2 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio loop ext4 jbd2 mbcache xt_CHECKSUM

fsx tests on DAX started to fail with msync failure on 0307 -next tree

2017-03-13 Thread Xiong Zhou
Hi, xfstests cases: generic/075 generic/112 generic/127 generic/231 generic/263 fail with DAX, pass without it. Both xfs and ext4. It was okay on 0306 -next tree. + ./check generic/075 FSTYP -- xfs (non-debug) PLATFORM -- Linux/x86_64 hp-dl360g9-12 4.11.0-rc1-linux-next-5be4921-ne

Re: [PATCH 0/2] fix for direct-I/O to DAX mappings

2017-03-02 Thread Xiong Zhou
On Sat, Feb 25, 2017 at 09:08:28AM -0800, Dan Williams wrote: > Hi Andrew, > > While Ross was doing a review of a new mmap+DAX direct-I/O test case for > xfstests, from Xiong, he noticed occasions where it failed to trigger a > page dirty event. Dave then spotted the problem fixed by patch1. The

Re: boot failure, module: overflow in relocation

2017-03-02 Thread Xiong Zhou
Nevermind, it got fixed now i think. On Thu, Mar 02, 2017 at 05:51:27PM +0800, Xiong Zhou wrote: > Hi, > > One host failed to boot while merge going on, > > [ 13.076303] module: overflow in relocation type 10 val a0060e58 > [ 13.076338] module: overflow in relo

boot failure, module: overflow in relocation

2017-03-02 Thread Xiong Zhou
Hi, One host failed to boot while merge going on, [ 13.076303] module: overflow in relocation type 10 val a0060e58 [ 13.076338] module: overflow in relocation type 10 val a01ac96b [ 13.076340] module: `scsi_transport_sas' likely not compiled with -mcmodel=kernel [ 13.1815

Re: mm allocation failure and hang when running xfstests generic/269 on xfs

2017-03-02 Thread Xiong Zhou
On Thu, Mar 02, 2017 at 09:42:23AM +0100, Michal Hocko wrote: > On Thu 02-03-17 12:17:47, Anshuman Khandual wrote: > > On 03/02/2017 10:49 AM, Xiong Zhou wrote: > > > On Wed, Mar 01, 2017 at 04:37:31PM -0800, Christoph Hellwig wrote: > > >> On Wed, Mar 01, 2017 a

Re: mm allocation failure and hang when running xfstests generic/269 on xfs

2017-03-01 Thread Xiong Zhou
On Wed, Mar 01, 2017 at 04:37:31PM -0800, Christoph Hellwig wrote: > On Wed, Mar 01, 2017 at 12:46:34PM +0800, Xiong Zhou wrote: > > Hi, > > > > It's reproduciable, not everytime though. Ext4 works fine. > > On ext4 fsstress won't run bulkstat because it doe

mm allocation failure and hang when running xfstests generic/269 on xfs

2017-02-28 Thread Xiong Zhou
Hi, It's reproduciable, not everytime though. Ext4 works fine. Based on test logs, it's bad on Linus tree commit: e5d56ef Merge tag 'watchdog-for-linus-v4.11' It's good on commit: f8e6859 Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc Trying to narrow down a little bit. Th

Ext4 new shutdown ioctl fails generic/04{4,5,6}

2017-02-27 Thread Xiong Zhou
Hi, On latest Linus tree, xfstests generic/04{4,5,6} fails. FSTYP -- ext4 PLATFORM -- Linux/x86_64 rhel73 4.10.0-master-45554b2+ MKFS_OPTIONS -- /dev/sdc MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:nfs_t:s0 /dev/sdc /test2 generic/045 - output mismatch (se

LTP write03 writev07 xfs failures

2017-02-26 Thread Xiong Zhou
Hi, These 2 tests PASS on Linus tree commit: 37c8596 Merge tag 'tty-4.11-rc1' of git://git.kernel.org/pub/scm/linux... FAIL on commit: 60e8d3e Merge tag 'pci-v4.11-changes' of git://git.kernel.org/pub/scm/... LTP latest commit: c60d3ca move_pages12: include lapi/mmap.h Steps: sh-4.2# pwd /r

LTP write03 writev07 xfs failures

2017-02-26 Thread Xiong Zhou
Hi, These 2 tests PASS on Linus tree commit: 37c8596 Merge tag 'tty-4.11-rc1' of git://git.kernel.org/pub/scm/linux... FAIL on commit: 60e8d3e Merge tag 'pci-v4.11-changes' of git://git.kernel.org/pub/scm/... LTP latest commit: c60d3ca move_pages12: include lapi/mmap.h Steps: sh-4.2# pwd /r

Re: Starting kvm/qemu guest crash kernel linux-next 0221 tree

2017-02-22 Thread Xiong Zhou
On Wed, Feb 22, 2017 at 09:28:21AM +0100, Paolo Bonzini wrote: > > > On 22/02/2017 02:52, Xiong Zhou wrote: > > Hi, > > > > Starting a guest begin to crash kernel on 0221 -next tree. > > > > It's fine on 0220 tree. I reproduced only once. Now it&#

Starting kvm/qemu guest crash kernel linux-next 0221 tree

2017-02-21 Thread Xiong Zhou
Hi, Starting a guest begin to crash kernel on 0221 -next tree. It's fine on 0220 tree. Thanks, Xiong - Feb 22 09:24:29 host-12 systemd-journald[405]: Received SIGTERM from PID 1 (systemd). Feb 22 09:24:29 host-12 kernel: systemd: 24 output lines suppressed due to ratelimiting Feb

Re: linux-next 0112 tree breaks fs DAX

2017-01-16 Thread Xiong Zhou
On Fri, Jan 13, 2017 at 06:16:41PM +0800, Xiong Zhou wrote: > Hi, > > These cases "hang" when testing with -o dax mount option: > xfstests generic/030 generic/34{0,4,5,6} generic/198 > (maybe more) > > The test programme holetest or aiodio keep running for a >

Re: [PATCH] dax: fix deadlock with DAX 4k holes

2017-01-04 Thread Xiong Zhou
ransition from > locking based on the DAX empty entry to locking on the 4k zero page. > > With the test case reported by Xiong this happens very regularly in my test > setup, with some runs resulting in 9+ threads in this deadlocked state. > With this fix I've been able to run t

Re: LTP rwtest01 blocks on DAX mountpoint

2017-01-04 Thread Xiong Zhou
On Tue, Jan 03, 2017 at 09:57:10AM -0700, Ross Zwisler wrote: > On Tue, Jan 03, 2017 at 02:49:22PM +0800, Xiong Zhou wrote: > > On Mon, Jan 02, 2017 at 02:49:41PM -0700, Ross Zwisler wrote: > > > On Mon, Jan 02, 2017 at 06:16:17PM +0100, Jan Kara wrote: > > > > On Fri

Re: LTP rwtest01 blocks on DAX mountpoint

2017-01-03 Thread Xiong Zhou
On Tue, Jan 03, 2017 at 09:57:10AM -0700, Ross Zwisler wrote: > On Tue, Jan 03, 2017 at 02:49:22PM +0800, Xiong Zhou wrote: > > On Mon, Jan 02, 2017 at 02:49:41PM -0700, Ross Zwisler wrote: > > > On Mon, Jan 02, 2017 at 06:16:17PM +0100, Jan Kara wrote: > > > > On Fri

Re: LTP rwtest01 blocks on DAX mountpoint

2017-01-03 Thread Xiong Zhou
On Tue, Jan 03, 2017 at 09:57:10AM -0700, Ross Zwisler wrote: > On Tue, Jan 03, 2017 at 02:49:22PM +0800, Xiong Zhou wrote: > > On Mon, Jan 02, 2017 at 02:49:41PM -0700, Ross Zwisler wrote: > > > On Mon, Jan 02, 2017 at 06:16:17PM +0100, Jan Kara wrote: > > > > On Fri

Re: LTP rwtest01 blocks on DAX mountpoint

2017-01-02 Thread Xiong Zhou
On Mon, Jan 02, 2017 at 02:49:41PM -0700, Ross Zwisler wrote: > On Mon, Jan 02, 2017 at 06:16:17PM +0100, Jan Kara wrote: > > On Fri 30-12-16 17:33:53, Xiong Zhou wrote: > > > On Sat, Dec 24, 2016 at 07:07:14PM +0800, Xiong Zhou wrote: > > > > Hi lists, snip > >

Re: LTP rwtest01 blocks on DAX mountpoint

2016-12-30 Thread Xiong Zhou
On Sat, Dec 24, 2016 at 07:07:14PM +0800, Xiong Zhou wrote: > Hi lists, > > Since around 20161129 tag, LTP rwtest01 on dax mountpoint blocks > on linux-next tree, now on Linus tree. > > In "normal", rwtest01 subcase ends in a few minutes, now it keeps > running fo

LTP rwtest01 blocks on DAX mountpoint

2016-12-24 Thread Xiong Zhou
Hi lists, Since around 20161129 tag, LTP rwtest01 on dax mountpoint blocks on linux-next tree, now on Linus tree. In "normal", rwtest01 subcase ends in a few minutes, now it keeps running for hours on dax mountpoint, both ext4 and xfs. Ctrl + c can interrupt it. It is always reproducible, blocki

multi-threads libvmmalloc fork test hang

2016-10-27 Thread Xiong Zhou
# description nvml test suite vmmalloc_fork test hang. $ ps -eo stat,comm | grep vmma S+ vmmalloc_fork Sl+ vmmalloc_fork Z+ vmmalloc_fork Sl+ vmmalloc_fork Z+ vmmalloc_fork Z+ vmmalloc_fork Sl+ vmmalloc_fork Z+ vmmalloc_fork Z+ vmmalloc_fork Z+ vmmalloc_fork dmesg: [ 2

xfstests xfs fuzzers fail with DAX

2016-08-03 Thread Xiong Zhou
Hi, A few xfs fuzzers in xfstests fail with dax mount option, pass without dax. They are xfs/086 xfs/088 xfs/089 xfs/091. xfstests to commit 4470ad4c7e (Jul 26) kernel to commit dd95069545 (Jul 24) + ./check xfs/091 FSTYP -- xfs (non-debug) PLATFORM -- Linux/x86_64 rhel73 4.7.0+

Re: [PATCH] Fix reported kmemleak

2016-06-12 Thread Xiong Zhou
branch: v4.7-rc2+bio_put > > Cc: Christoph Hellwig > Cc: ax...@kernel.dk > cc: David Drysdale > Cc: Xiong Zhou Thanks for the information! > Cc: Stephen Rothwell > Cc: linux-n...@vger.kernel.org > Cc: linux-nvd...@ml01.01.org > Cc: Christoph Hellwig > Cc: Larr

Re: linux-next/linux memleak after IO on dax mountpoint

2016-06-07 Thread Xiong Zhou
adding block-list On Fri, Jun 03, 2016 at 09:48:27AM -0700, Bart Van Assche wrote: > On 06/02/2016 08:22 AM, David Drysdale wrote: > > FWIW, I'm also seeing kmemleak report a leak with v4.7-rc1, in > > a different scenario (just normal desktop use). Not done much > > digging so far, but this comm

Re: linux-next/linux memleak after IO on dax mountpoint

2016-06-02 Thread Xiong Zhou
On Thu, Jun 02, 2016 at 04:22:37PM +0100, David Drysdale wrote: > On Sat, May 28, 2016 at 5:05 AM, Xiong Zhou wrote: > > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > > ... > >> Still working on to id which commit in this merge causes this issuer,

Re: linux-next memleak after IO on dax mountpoint

2016-06-01 Thread Xiong Zhou
Hi, Jeff On Wed, Jun 01, 2016 at 10:37:26AM -0400, Jeff Moyer wrote: > Xiong Zhou writes: > > > On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: > > ... > >> Still working on to id which commit in this merge causes this issuer, > > > > Narrow

Re: linux-next memleak after IO on dax mountpoint

2016-05-27 Thread Xiong Zhou
On Fri, May 27, 2016 at 04:46:17PM +0800, Xiong Zhou wrote: ... > Still working on to id which commit in this merge causes this issuer, Narrowed down to: 37e5823 block: add offset in blk_add_request_payload() e048948 blk-mq: Export tagset iter function 58b4560 nvme: add helper nvme_map_

linux-next memleak after IO on dax mountpoint

2016-05-27 Thread Xiong Zhou
Hi, Reporting an oom/memleak issue in linux-next tree: #Description: dbench invokes oom-killer, make host unavaiable. dbench was doing IO on nvdimm device mounted fs with dax mount option. It happens on both xfs and ext4 filesystems. It does not happen testing without dax mountoption. Seems li

Re: linux-next: Tree for May 17

2016-05-23 Thread Xiong Zhou
Hi Stephen, On Mon, May 23, 2016 at 4:37 PM, Stephen Rothwell wrote: > Hi Xiong, > > On Mon, 23 May 2016 16:13:28 +0800 Xiong Zhou wrote: >> >> hi, >> >> On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell >> wrote: >> > >> > I have cre

Re: linux-next: Tree for May 17

2016-05-23 Thread Xiong Zhou
hi, On Tue, May 17, 2016 at 1:04 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any v4.8 destined material to your linux-next included > branches until after v4.7-rc1 has been released. > > Changes since 20160516: > > The vfs tree gained a conflict against the ext4 tree. > > The net-

Re: [PATCH v3 2/5] /dev/dax, pmem: direct access to persistent memory

2016-05-20 Thread Xiong Zhou
On Wed, May 18, 2016 at 01:56:16PM -0700, Dan Williams wrote: > Device DAX is the device-centric analogue of Filesystem DAX > (CONFIG_FS_DAX). It allows memory ranges to be allocated and mapped > without need of an intervening file system. Device DAX is strict, > precise and predictable. Specifi

Re: Linux-next parallel cp workload hang

2016-05-18 Thread Xiong Zhou
On Thu, May 19, 2016 at 09:02:31AM +1000, Dave Chinner wrote: > On Thu, May 19, 2016 at 12:17:26AM +1000, Dave Chinner wrote: > > Patch below should fix the deadlock. > > The test has been running for several hours without failure using > this patch, so I'd say this fixes the problem... Yes, the

Linux-next parallel cp workload hang

2016-05-17 Thread Xiong Zhou
Hi, Parallel cp workload (xfstests generic/273) hangs like blow. It's reproducible with a small chance, less the 1/100 i think. Have hit this in linux-next 20160504 0506 0510 trees, testing on xfs with loop or block device. Ext4 survived several rounds of testing. Linux next 20160510 tree hangs

Re: [PATCH trivial] scripts/prune-kernel: remove kdump images

2016-04-25 Thread Xiong Zhou
ping ? On Mon, Mar 7, 2016 at 3:56 PM, Xiong Zhou wrote: > Signed-off-by: Xiong Zhou > --- > scripts/prune-kernel | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/scripts/prune-kernel b/scripts/prune-kernel > index ab5034e..9c67be2 100755 > --

Re: binary execution from DAX mount hang since next-20160407

2016-04-17 Thread Xiong Zhou
On Fri, Apr 15, 2016 at 4:38 PM, Hugh Dickins wrote: > On Fri, 15 Apr 2016, Xiong Zhou wrote: > >> Hi, all >> >> Since tag next-20160407 in linux-next repo, executing binary >> from/in DAX mount hangs. >> >> It does not hang if mount without dax option.

Re: binary execution from DAX mount hang since next-20160407

2016-04-14 Thread Xiong Zhou
# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.6.0-rc3-next-20160414+ root=/dev/mapper/x--01-root ro crashkernel=auto rd.lvm.lv=x-01/root rd.lvm.lv=xx/swap console=ttyS1,115200n81 memmap=10G!5G memmap=15G!15G selinux=0 LANG=en_US.UTF-8 # mkfs.ext4 -V mke2fs 1.43-WIP (15-Mar-2016) Using EXT2

Re: [-next] BUG_ON in scsi_target_destroy()

2016-04-14 Thread Xiong Zhou
Hi, On Wed, Apr 13, 2016 at 11:14 PM, James Bottomley wrote: > On Wed, 2016-04-13 at 10:41 +0200, Johannes Thumshirn wrote: >> Hi Sergey, Xiong, >> >> Can you try below patch? >> >> On Montag, 11. April 2016 18:01:47 CEST Sergey Senozhatsky wrote: >> > Hello, >> > >> > commit 7b106f2de6938c31ce5

Re: [-next] BUG_ON in scsi_target_destroy()

2016-04-14 Thread Xiong Zhou
Hi, On Wed, Apr 13, 2016 at 4:41 PM, Johannes Thumshirn wrote: > Hi Sergey, Xiong, > > Can you try below patch? This survives modprobe -r scsi_debug. > > On Montag, 11. April 2016 18:01:47 CEST Sergey Senozhatsky wrote: >> Hello, >> >> commit 7b106f2de6938c31ce5e9c86bc70ad3904666b96 >> Author:

Re: [PATCH v4 1/2] scsi: Add intermediate STARGET_REMOVE state to scsi_target_state

2016-04-14 Thread Xiong Zhou
On Wed, Apr 13, 2016 at 4:19 PM, Johannes Thumshirn wrote: > Hi Xiong > Sorry for the late reply > > On Dienstag, 12. April 2016 21:01:53 CEST Xiong Zhou wrote: >> How about this? >> >> drivers/scsi/scsi_scan: mark STARGET_REMOVE state before destroy &

Re: [PATCH v4 1/2] scsi: Add intermediate STARGET_REMOVE state to scsi_target_state

2016-04-12 Thread Xiong Zhou
How about this? drivers/scsi/scsi_scan: mark STARGET_REMOVE state before destroy Signed-off-by: Xiong Zhou --- drivers/scsi/scsi_scan.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c index 27df7e7..21092e5 100644 --- a/drivers/scsi

Re: [PATCH v4 1/2] scsi: Add intermediate STARGET_REMOVE state to scsi_target_state

2016-04-11 Thread Xiong Zhou
Hi, On Tue, Apr 5, 2016 at 5:50 PM, Johannes Thumshirn wrote: > Add intermediate STARGET_REMOVE state to scsi_target_state to avoid > running into the BUG_ON() in scsi_target_reap(). The STARGET_REMOVE > state is only valid in the path from scsi_remove_target() to > scsi_target_destroy() indicati

Re: 4.5.0+ panic when setup loop device

2016-03-19 Thread Xiong Zhou
Hi, On Thu, Mar 17, 2016 at 7:39 PM, Thomas Gleixner wrote: > B1;2802;0cOn Thu, 17 Mar 2016, Peter Zijlstra wrote: > >> On Thu, Mar 17, 2016 at 11:21:24AM +0100, Thomas Gleixner wrote: >> > On Thu, 17 Mar 2016, Peter Zijlstra wrote: >> > >> > > Could you please try? I'm not sure how this would ex

[PATCH trivial] scripts/prune-kernel: remove kdump images

2016-03-06 Thread Xiong Zhou
Signed-off-by: Xiong Zhou --- scripts/prune-kernel | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/prune-kernel b/scripts/prune-kernel index ab5034e..9c67be2 100755 --- a/scripts/prune-kernel +++ b/scripts/prune-kernel @@ -14,7 +14,7 @@ do echo

ext2/3 using ext4 module mkdir IO error on pmem DAX mount

2016-03-01 Thread Xiong Zhou
Hi, mkdir failed IO error on pmem DAX ext2/3 fs mount using ext4 module. This happends only on -next tree, not on Linus' tree, at least from 4.5.0-rc5-next-20160224. .config attached. sh-4.2# uname -r 4.5.0-rc6-next-20160301 sh-4.2# sh -x extmod.sh + testmkdir ext2 /dev/pmem0 /daxmnt ext4 + mkd

[PATCH] staging: android: logger: fix kuid/uid in logger_entry

2014-10-29 Thread Xiong Zhou
From: Xiong Zhou struct logger_entry can be returned to userspace via ioctl, so it is wrong to have a kuid_t member, fixing it to uid_t. This was introduced by commit bd471258f2, to pass uidguid type checks : UIDGID_STRICT_TYPE_CHECKS, which has been removed from kernel in commit 261000a56b6

Re: [vfs] WARNING: CPU: 3 PID: 2339 at mm/truncate.c:758 pagecache_isize_extended+0xdd/0x120()

2014-10-27 Thread Xiong Zhou
still in rc2 [ cut here ] WARNING: CPU: 0 PID: 18152 at mm/truncate.c:758 pagecache_isize_extended+0xfd/0x110() Modules linked in: btrfs xor zlib_deflate raid6_pq ntfs fuse x86_pkg_temp_thermal wmi radeon e1000e ttm CPU: 0 PID: 18152 Comm: Cache I/O Tainted: GW

[PATCH v2] nfs: remove redundant slash from nfs_path

2014-08-24 Thread Xiong Zhou
When export root dir(/) via nfs, and mount a particular dir under root, eg /nfsexport, there will be defect double slash output in /proc/mounts, like localhost://nfsexport. While this patch change it to localhost:/nfsexport. Signed-off-by: Xiong Zhou --- fs/nfs/namespace.c | 2 +- 1 file

[PATCH] nfs: use canonical path in nfs_show_devname

2014-08-19 Thread Xiong Zhou
When export root dir(/) via nfs, and mount a particular dir under root, eg /nfsexport, there will be defect double slash output in /proc/mounts, like localhost://nfsexport. Signed-off-by: Xiong Zhou --- fs/nfs/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/nfs

Re: [xen] double fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC

2013-10-23 Thread Xiong Zhou
How is this going? regards, 2013/10/11 Fengguang Wu : >> I think something like the below may address the issue - I've only build >> tested this so far. >> >> We have another case where DRM does the wrong thing here too - a similar >> thing goes on with connectors as well. I've not yet looked

[PATCH] amilo-rfkill: add Kconfig depends on i8042

2013-08-20 Thread Xiong Zhou
From: Xiong Zhou Fix randconfig build failure for Amilo x86 platform driver. AMILO_RFKILL requires SERIO_I8042 being available. amilo-rfkill.c:(.text+0x108b5b): undefined reference to `i8042_lock_chip' amilo-rfkill.c:(.text+0x108b69): undefined reference to `i8042_command' amilo-rfkil

[PATCH] staging/lustre: lloop depends on BLOCK

2013-08-01 Thread Xiong Zhou
From: Xiong Zhou Add a config option for llite/lloop in lustre driver, making it depends on BLOCK to fix this better: drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2: error: implicit declaration of function ‘unregister_blkdev' Also, remove the wr

Re: [PATCH v2] staging/lustre: lloop depends on BLOCK

2013-08-01 Thread Xiong Zhou
On Wed, 31 Jul 2013, Greg Kroah-Hartman wrote: > On Wed, Jul 31, 2013 at 10:30:41AM +0800, Xiong Zhou wrote: > > From: Xiong Zhou > > > > First version of this patch makes LUSTRE_FS depends on BLOCK. Second > > version makes only lloop depends on BLOCK wi

Re: [PATCH v2] staging/lustre: lloop depends on BLOCK

2013-07-30 Thread Xiong Zhou
On Tue, 30 Jul 2013, Peng Tao wrote: > On Tue, Jul 30, 2013 at 8:29 AM, Xiong Zhou wrote: > > From: Xiong Zhou > > > > In the lustre client driver, lloop depends on BLOCK. Add an > > option for this dependence. Last version of this patch makes > > LUSTR

[PATCH] include/jbd: add missing ifdef CONFIG_BLOCK

2013-07-29 Thread Xiong Zhou
From: Xiong Zhou In jbd{2}.h, BH_PrivateStart is used in the define of enum jbd_state_bits, which is defined in buffer_head.h under ifdef CONFIG_BLOCK. In these two headers, BUFFER_FNS and TAS_BUFFER_FNS and jbd_common.h refer to enum jbd_state_bits, so they should under ifdef CONFIG_BLOCK

[PATCH v2] staging/lustre: lloop depends on BLOCK

2013-07-29 Thread Xiong Zhou
From: Xiong Zhou In the lustre client driver, lloop depends on BLOCK. Add an option for this dependence. Last version of this patch makes LUSTRE_FS depends on BLOCK. Remove unnecessary jdb head files which depends on BLOCK. Signed-off-by: Xiong Zhou --- drivers/staging/lustre/lustre/Kconfig

Re: [PATCH] staging/lustre: add BLOCK depends in Kconfig

2013-07-25 Thread Xiong Zhou
2013/7/26 Dilger, Andreas : > On 2013/07/25 1:06 AM, "Xiong Zhou" wrote: > >>From: Xiong Zhou >> >>Add BLOCK depends in Kconfig for LUSTRE to fix this: >>drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2 >>: >>error:

Re: [PATCH] staging/lustre: add BLOCK depends in Kconfig

2013-07-25 Thread Xiong Zhou
2013/7/25 Paul Bolle : > On Thu, 2013-07-25 at 15:06 +0800, Xiong Zhou wrote: >> Add BLOCK depends in Kconfig for LUSTRE to fix this: >> drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2: >> error: implicit declaration of function ‘unregister_blkdev

[PATCH] staging/lustre: add BLOCK depends in Kconfig

2013-07-25 Thread Xiong Zhou
From: Xiong Zhou Add BLOCK depends in Kconfig for LUSTRE to fix this: drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2: error: implicit declaration of function ‘unregister_blkdev’ Signed-off-by: Xiong Zhou --- drivers/staging/lustre/lustre/Kconfig |2 +- 1 file

[tip:x86/urgent] x86/platform/ce4100: Add header file for reboot type

2013-07-12 Thread tip-bot for Xiong Zhou
Commit-ID: ff5599816711d2e67da2d7561fd36ac48debd433 Gitweb: http://git.kernel.org/tip/ff5599816711d2e67da2d7561fd36ac48debd433 Author: Xiong Zhou AuthorDate: Tue, 9 Jul 2013 11:06:27 +0800 Committer: Ingo Molnar CommitDate: Fri, 12 Jul 2013 12:21:20 +0200 x86/platform/ce4100: Add

Re: [PATCH] x86: ce4100: add head file for reboot type

2013-07-11 Thread Xiong Zhou
2013/7/9 Xiong Zhou : > From: Xiong Zhou > > Add head file for reboot type stuff to fix this: > error: ‘reboot_type’ undeclared (first use in this function) > error: ‘BOOT_KBD’ undeclared (first use in this function) > > Signed-off-by: Xiong Zhou > --- > arch/x86/plat

Re: [PATCH]amilo-rfkill: add depends on i8042 in Kconfig

2013-07-11 Thread Xiong Zhou
2013/6/28 Randy Dunlap : > On 06/18/13 18:09, Xiong Zhou wrote: >> 2013/6/18 Randy Dunlap : >>> On 06/18/13 06:04, Ben Hutchings wrote: >>>> On Tue, 2013-06-18 at 17:21 +0800, Xiong Zhou wrote: >>>>> From: Xiong Zhou >>>>> >

[PATCH] x86: ce4100: add head file for reboot type

2013-07-08 Thread Xiong Zhou
From: Xiong Zhou Add head file for reboot type stuff to fix this: error: ‘reboot_type’ undeclared (first use in this function) error: ‘BOOT_KBD’ undeclared (first use in this function) Signed-off-by: Xiong Zhou --- arch/x86/platform/ce4100/ce4100.c |1 + 1 file changed, 1 insertion

Re: [PATCH]amilo-rfkill: add depends on i8042 in Kconfig

2013-06-18 Thread Xiong Zhou
2013/6/18 Randy Dunlap : > On 06/18/13 06:04, Ben Hutchings wrote: >> On Tue, 2013-06-18 at 17:21 +0800, Xiong Zhou wrote: >>> From: Xiong Zhou >>> >>> Fix randconfig build failure for Amilo x86 platform driver. >>> AMILO_RFKILL requires SERIO_I8042 b

[PATCH]amilo-rfkill: add depends on i8042 in Kconfig

2013-06-18 Thread Xiong Zhou
From: Xiong Zhou Fix randconfig build failure for Amilo x86 platform driver. AMILO_RFKILL requires SERIO_I8042 being available. amilo-rfkill.c:(.text+0x108b5b): undefined reference to `i8042_lock_chip' amilo-rfkill.c:(.text+0x108b69): undefined reference to `i8042_command' amilo-rfkil

[PATCH] staging/solo6x10: select the desired font

2013-05-17 Thread Xiong Zhou
From: Xiong Zhou Make sure FONT_8x16 can be found by find_font(). Signed-off-by: Xiong Zhou --- drivers/staging/media/solo6x10/Kconfig |1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/media/solo6x10/Kconfig b/drivers/staging/media/solo6x10/Kconfig index ec32776..0bc743b

Re: linux-next: Tree for May 15 (crypto /crct10dif)

2013-05-16 Thread Xiong Zhou
2013/5/17 Tim Chen : > On Thu, 2013-05-16 at 09:59 -0700, Tim Chen wrote: >> On Thu, 2013-05-16 at 09:22 +0200, Geert Uytterhoeven wrote: >> > On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou >> > wrote: >> > > --- a/crypto/Kconfig >> > > +++

Re: linux-next: Tree for May 15 (crypto /crct10dif)

2013-05-16 Thread Xiong Zhou
2013/5/16 Geert Uytterhoeven : > On Thu, May 16, 2013 at 5:57 AM, Xiong Zhou wrote: >> --- a/crypto/Kconfig >> +++ b/crypto/Kconfig >> @@ -378,6 +378,7 @@ config CRYPTO_CRC32_PCLMUL >> >> config CRYPTO_CRCT10DIF >> tristate "CRCT10DIF algorith

Re: linux-next: Tree for May 15 (crypto /crct10dif)

2013-05-15 Thread Xiong Zhou
to `crc_t10dif_generic' > > > CONFIG_CRYPTO_CRCT10DIF=y > CONFIG_CRC_T10DIF=m > > > > Full randconfig file is attached. > > > -- > ~Randy > just try. From: Xiong Zhou Try to fix randconfig build error reported by Randy Dunlap: on x86_64: crypto/built-in

Re: linux-next: Tree for May 9

2013-05-09 Thread Xiong Zhou
On Thu, 9 May 2013, Stephen Rothwell wrote: > Hi all, > > Please do not add any v3.11 destined work to your linux-next included > branches until after v3.10-rc1 is released. > > Changes since 20130508: > > The microblaze tree gained a conflict against Linus' tree > > The regmap tree gained a

Re: [PATCH] staging: android: logger: use kuid_t instead of uid_t

2013-05-08 Thread Xiong Zhou
Thanks all for reviewing. xiong 2013/5/8 Greg KH : > On Wed, May 08, 2013 at 06:52:48PM +0800, Xiong Zhou wrote: >> From: Xiong Zhou >> >> Use kuid_t instead of uid_t, to pass the UIDGID_STRICT_TYPE_CHECKS. >> >> Signed-off-by: Xiong Zhou > > Nice job, I

[PATCH] staging: android: logger: use kuid_t instead of uid_t

2013-05-08 Thread Xiong Zhou
From: Xiong Zhou Use kuid_t instead of uid_t, to pass the UIDGID_STRICT_TYPE_CHECKS. Signed-off-by: Xiong Zhou --- drivers/staging/android/logger.c |4 ++-- drivers/staging/android/logger.h |2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/android

Re: [PATCH -next] power: fix bq27x00_battery kconfig

2013-05-06 Thread Xiong Zhou
From: Xiong Zhou This patch fixes build failure(randconfig) of next-20130501. When config I2C as m, BATTERY_BQ27x00 as y, here comes the failure. The driver depends on I2C only if I2C is not disabled, as Lars commented. Last version of this patch make the driver depend on I2C unconditionally

[PATCH -next] power: fix bq27x00_battery kconfig

2013-05-03 Thread Xiong Zhou
From: Xiong Zhou This patch fixes build failure(randconfig) of next-20130501. When config I2C as m, BATTERY_BQ27x00 as y, here comes the failure. BATTERY_BQ27x00 depends on I2C according to the code. Failure message: drivers/built-in.o: In function `bq27x00_read_i2c': bq27x00_battery.c:(

[PATCH v2] gma500:fix build failure for 3.9-rc5

2013-04-10 Thread Xiong Zhou
From: Xiong Zhou Last version of this patch is not clear enough and X86 duplicated. This patch fixes build failure of v3.9-rc5 and rc6. When config ACPI_VIDEO as m, DRM_GMA500 as y, here comes the failure. GMA5/600 needs acpi_video just like nouveau. And some tab type fix by the way. Failure

Re: [PATCH] drivers/gpu/drm/gma500:fix build failure for 3.9-rc5

2013-04-10 Thread Xiong Zhou
On Tue, 9 Apr 2013, Patrik Jakobsson wrote: > On Tue, Apr 9, 2013 at 8:35 AM, Xiong Zhou wrote: > > From: Xiong Zhou > > > > This patch fixes build failure of v3.9-rc5. > > When config ACPI_VIDEO as m, DRM_GMA500 as y, here comes the failure. > > gma5/600 n

[PATCH] drivers/gpu/drm/gma500:fix build failure for 3.9-rc5

2013-04-08 Thread Xiong Zhou
From: Xiong Zhou This patch fixes build failure of v3.9-rc5. When config ACPI_VIDEO as m, DRM_GMA500 as y, here comes the failure. gma5/600 needs acpi_video just like nouveau. Failure message: drivers/built-in.o: In function `psb_driver_load': kernel-3.9-rc5/drivers/gpu/drm/gma500/psb_drv.

[PATCH] drivers/gpu/drm/gma500:fix build failure for 3.9-rc5

2013-04-06 Thread Xiong Zhou
From: Xiong Zhou This patch fixes build failure of v3.9-rc5. When config ACPI_VIDEO as m, DRM_GMA500 as y, here comes the failure. gma5/600 needs acpi_video just like nouveau. Failure message: drivers/built-in.o: In function `psb_driver_load': kernel-3.9-rc5/drivers/gpu/drm/gma500/psb_drv.

[patch v2] sound/soc/codecs : fix build failure for next-20130325

2013-03-27 Thread Xiong Zhou
From: Xiong Zhou This patch fixes build failure of next-20130325 (and also next-20130322), about sound soc codec modules. I try to fix this by moving arrays to the header last time. Failing message: ERROR: "arizona_rate_text" [sound/soc/codecs/snd-soc-wm-adsp.ko] undefine

Re: [patch] sound/soc/codec : fix build failure in next-201303225

2013-03-25 Thread Xiong Zhou
On Mon, 25 Mar 2013, Mark Brown wrote: > On Mon, Mar 25, 2013 at 07:59:43PM +0800, Xiong Zhou wrote: > > > -const char *arizona_rate_text[ARIZONA_RATE_ENUM_SIZE] = { > > - "SYNCCLK rate", "8kHz", "16kHz", "ASYNCCLK rat

[patch] sound/soc/codec : fix build failure in next-201303225

2013-03-25 Thread Xiong Zhou
From: Xiong Zhou This patch fixes build failure of next-20130325 (and also next-20130322), about sound soc codec modules, based on previous implementation. Failing message: MODPOST 2490 modules ERROR: "arizona_rate_text" [sound/soc/codecs/snd-soc-wm-adsp.ko] undefine