Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Stephen Rothwell
Hi all, On Mon, 2 May 2016 22:07:45 +1000 Stephen Rothwell wrote: > > This comes from a bad automatic merge resolution between commit > > d101a125954e ("fs: add file_dentry()") > > from Linus' tree (introduced before v4.5-rc3) and commit

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Stephen Rothwell
Hi all, On Mon, 2 May 2016 22:07:45 +1000 Stephen Rothwell wrote: > > This comes from a bad automatic merge resolution between commit > > d101a125954e ("fs: add file_dentry()") > > from Linus' tree (introduced before v4.5-rc3) and commit

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Sergey Senozhatsky
On (05/02/16 22:07), Stephen Rothwell wrote: [..] > > The issue is that 2 macros have the same value: > > > > #define DCACHE_OP_REAL 0x0800 > > > > #define DCACHE_PAR_LOOKUP 0x0800 /* being looked up > > (with parent locked shared) */ > > > > Verified with

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Sergey Senozhatsky
On (05/02/16 22:07), Stephen Rothwell wrote: [..] > > The issue is that 2 macros have the same value: > > > > #define DCACHE_OP_REAL 0x0800 > > > > #define DCACHE_PAR_LOOKUP 0x0800 /* being looked up > > (with parent locked shared) */ > > > > Verified with

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Stephen Rothwell
Hi Mateusz, On Mon, 2 May 2016 12:33:54 +0200 Mateusz Guzik wrote: > > On Mon, May 02, 2016 at 07:15:24PM +0900, Sergey Senozhatsky wrote: > > On (05/02/16 18:40), Stephen Rothwell wrote: > > > Hi all, > > > > > > Changes since 20160429 > > > > Hello, > > > > [

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Stephen Rothwell
Hi Mateusz, On Mon, 2 May 2016 12:33:54 +0200 Mateusz Guzik wrote: > > On Mon, May 02, 2016 at 07:15:24PM +0900, Sergey Senozhatsky wrote: > > On (05/02/16 18:40), Stephen Rothwell wrote: > > > Hi all, > > > > > > Changes since 20160429 > > > > Hello, > > > > [0.368791] [

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Mateusz Guzik
On Mon, May 02, 2016 at 07:15:24PM +0900, Sergey Senozhatsky wrote: > On (05/02/16 18:40), Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20160429 > > Hello, > > [0.368791] [ cut here ] > [0.368850] WARNING: CPU: 0 PID: 1 at fs/dcache.c:1688

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Mateusz Guzik
On Mon, May 02, 2016 at 07:15:24PM +0900, Sergey Senozhatsky wrote: > On (05/02/16 18:40), Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20160429 > > Hello, > > [0.368791] [ cut here ] > [0.368850] WARNING: CPU: 0 PID: 1 at fs/dcache.c:1688

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Sergey Senozhatsky
On (05/02/16 18:40), Stephen Rothwell wrote: > Hi all, > > Changes since 20160429 Hello, [0.368791] [ cut here ] [0.368850] WARNING: CPU: 0 PID: 1 at fs/dcache.c:1688 d_set_d_op+0x5e/0xcc [0.368911] Modules linked in: [0.369002] CPU: 0 PID: 1 Comm:

Re: linux-next: Tree for May 2 [WARNING: at fs/dcache.c]

2016-05-02 Thread Sergey Senozhatsky
On (05/02/16 18:40), Stephen Rothwell wrote: > Hi all, > > Changes since 20160429 Hello, [0.368791] [ cut here ] [0.368850] WARNING: CPU: 0 PID: 1 at fs/dcache.c:1688 d_set_d_op+0x5e/0xcc [0.368911] Modules linked in: [0.369002] CPU: 0 PID: 1 Comm: