Re: [v4.6-rc7-183-g1410b74e4061]

On 5/16/16, Sedat Dilek wrote: > On 5/16/16, Peter Zijlstra wrote: >> On Mon, May 16, 2016 at 07:42:35PM +0200, Sedat Dilek wrote: >> >>> Unfortunately, I could not reproduce this again with none of my >>> 183-kernels. >>> When I first hit

Re: [GIT] Networking

On 5/19/16, Reinoud Koornstra wrote: > On Thu, May 19, 2016 at 2:20 AM, Reinoud Koornstra > wrote: >> On Wed, May 18, 2016 at 12:51 PM, Linus Torvalds >> wrote: >>> On Wed, May 18, 2016 at 11:45 AM, Linus

Re: [GIT] Networking

On 5/19/16, Reinoud Koornstra wrote: > On Thu, May 19, 2016 at 2:20 AM, Reinoud Koornstra > wrote: >> On Wed, May 18, 2016 at 12:51 PM, Linus Torvalds >> wrote: >>> On Wed, May 18, 2016 at 11:45 AM, Linus Torvalds >>> wrote: From what I can tell, there's a merge bug in commit

Re: [v4.6-rc7-183-g1410b74e4061]

On 5/16/16, Peter Zijlstra <pet...@infradead.org> wrote: > On Mon, May 16, 2016 at 07:42:35PM +0200, Sedat Dilek wrote: > >> Unfortunately, I could not reproduce this again with none of my >> 183-kernels. >> When I first hit a "chain_key collision" issue,

Re: [v4.6-rc7-183-g1410b74e4061]

On 5/16/16, Peter Zijlstra wrote: > On Mon, May 16, 2016 at 07:42:35PM +0200, Sedat Dilek wrote: > >> Unfortunately, I could not reproduce this again with none of my >> 183-kernels. >> When I first hit a "chain_key collision" issue, it was hard to redproduce, &g

Re: [v4.6-rc7-183-g1410b74e4061]

On 5/16/16, Ingo Molnar <mi...@kernel.org> wrote: > > * Sedat Dilek <sedat.di...@gmail.com> wrote: > >> Hi, >> >> as Linux v4.6 is very near, I decided to write this bug report (only >> drunk one coffee). >> >> First, I am not absolute

Re: [v4.6-rc7-183-g1410b74e4061]

On 5/16/16, Ingo Molnar wrote: > > * Sedat Dilek wrote: > >> Hi, >> >> as Linux v4.6 is very near, I decided to write this bug report (only >> drunk one coffee). >> >> First, I am not absolutely sure if this is a real issue as... >>

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

0-rc1/4.5.4-rc1) will have it, too. - Sedat - > On Mon, May 2, 2016 at 11:39 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > >> On 4/25/16, Sedat Dilek <sedat.di...@gmail.com> wrote: >> > On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran >> > <hcoch...@ke

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

e it, too. - Sedat - > On Mon, May 2, 2016 at 11:39 AM, Sedat Dilek wrote: > >> On 4/25/16, Sedat Dilek wrote: >> > On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran >> > wrote: >> >> On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher >&g

Re: [PATCH 4.4 00/67] 4.4.10-stable review

On 5/10/16, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Tue, May 10, 2016 at 10:45:57AM +0200, Sedat Dilek wrote: >> Hi, >> >> I have tested with my usual setup/config on Ubuntu/precise AMD64. >> Looks good and ships [1]. >> >> Thanks.

Re: [PATCH 4.4 00/67] 4.4.10-stable review

On 5/10/16, Greg Kroah-Hartman wrote: > On Tue, May 10, 2016 at 10:45:57AM +0200, Sedat Dilek wrote: >> Hi, >> >> I have tested with my usual setup/config on Ubuntu/precise AMD64. >> Looks good and ships [1]. >> >> Thanks. >> >> Hope this f

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On 4/4/16, Peter Zijlstra <pet...@infradead.org> wrote: > On Mon, Apr 04, 2016 at 05:31:40PM +0200, Sedat Dilek wrote: >> > +/* https://en.wikipedia.org/wiki/Xorshift#xorshift.2A */ >> > +#define UINT64_C(x) x##ULL >> > +static inline u64 xorshift64star(u64

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On 4/4/16, Peter Zijlstra wrote: > On Mon, Apr 04, 2016 at 05:31:40PM +0200, Sedat Dilek wrote: >> > +/* https://en.wikipedia.org/wiki/Xorshift#xorshift.2A */ >> > +#define UINT64_C(x) x##ULL >> > +static inline u64 xorshift64star(u64 x) >> > +{ >> >

Re: [PATCH] compiler-gcc: require gcc 4.8 for powerpc __builtin_bswap16()

On 5/9/16, Stephen Rothwell wrote: > Hi Josh, > > On Fri, 6 May 2016 09:22:25 -0500 Josh Poimboeuf > wrote: >> >> I've also seen no problems on powerpc with 4.4 and 4.8. I suspect it's >> specific to gcc 4.6. Stephen, can you confirm this patch fixes

Re: [PATCH] compiler-gcc: require gcc 4.8 for powerpc __builtin_bswap16()

On 5/9/16, Stephen Rothwell wrote: > Hi Josh, > > On Fri, 6 May 2016 09:22:25 -0500 Josh Poimboeuf > wrote: >> >> I've also seen no problems on powerpc with 4.4 and 4.8. I suspect it's >> specific to gcc 4.6. Stephen, can you confirm this patch fixes it? > > That will obviously fix the problem

Re: [PATCH v4.6-rc] writeback: Fix performance regression in wb_over_bg_thresh()

or before the referenced commit. > > Fixes: 947e9762a8dd ("writeback: update wb_over_bg_thresh() to use wb_domain > aware operations") > Signed-off-by: Howard Cochran <hcoch...@kernelspring.com> > Acked-by: Tejun Heo <t...@kernel.org> > Signed-off-by: Miklos Szer

Re: [PATCH v4.6-rc] writeback: Fix performance regression in wb_over_bg_thresh()

("writeback: update wb_over_bg_thresh() to use wb_domain > aware operations") > Signed-off-by: Howard Cochran > Acked-by: Tejun Heo > Signed-off-by: Miklos Szeredi > Cc: # v4.2+ Fell free to add my... Tested-by Sedat Dilek - sed@ - > --- > mm/page-write

[PATCH 4.4 000/163] 4.4.9-stable review

>From [1]... [ QUOTE ] This is the start of the stable review cycle for the 4.4.9 release. There are 163 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu May 5 00:04:47

[PATCH 4.4 000/163] 4.4.9-stable review

>From [1]... [ QUOTE ] This is the start of the stable review cycle for the 4.4.9 release. There are 163 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu May 5 00:04:47

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On 4/25/16, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran > <hcoch...@kernelspring.com> wrote: >> On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher >> <jakob...@gmail.com> wrote: >>> On 12.04.2016 13:

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On 4/25/16, Sedat Dilek wrote: > On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran > wrote: >> On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher >> wrote: >>> On 12.04.2016 13:09, Tejun Heo wrote: >>>>> >>>>> Probably you wa

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran wrote: > On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher > wrote: >> On 12.04.2016 13:09, Tejun Heo wrote: Probably you want to look into: https://lkml.org/lkml/2016/3/10/21

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran wrote: > On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher > wrote: >> On 12.04.2016 13:09, Tejun Heo wrote: Probably you want to look into: https://lkml.org/lkml/2016/3/10/21 The patch mentioned above solves the issue

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

://lkml.org/lkml/2016/3/10/21 >> >> The patch mentioned above solves the issue for me. > > Heh, I tracked it down to wb_over_bg_thresh() and fell asleep. Yeah, > that is the right fix. > Feel free to add my... Tested-by: Sedat Dilek <sedat.di...@gmail.com> Patch available from [1]. - sed@ - [1] https://patchwork.kernel.org/patch/8554181/

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

patch mentioned above solves the issue for me. > > Heh, I tracked it down to wb_over_bg_thresh() and fell asleep. Yeah, > that is the right fix. > Feel free to add my... Tested-by: Sedat Dilek Patch available from [1]. - sed@ - [1] https://patchwork.kernel.org/patch/8554181/

Re: [tip.git#x86/debug] Re: x86/dumpstack: Combine some printk()s

On Sat, Apr 2, 2016 at 1:12 PM, Thomas Gleixner <t...@linutronix.de> wrote: > On Sat, 2 Apr 2016, Sedat Dilek wrote: > >> Hi, >> >> I was looking through tip Git tree... >> >> Why didn't you use... >> >> + IS_ENABLED(CONFIG_DEBUG_

Re: [tip.git#x86/debug] Re: x86/dumpstack: Combine some printk()s

On Sat, Apr 2, 2016 at 1:12 PM, Thomas Gleixner wrote: > On Sat, 2 Apr 2016, Sedat Dilek wrote: > >> Hi, >> >> I was looking through tip Git tree... >> >> Why didn't you use... >> >> + IS_ENABLED(CONFIG_DEBUG_PAGEAL

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 4:06 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 11:36:59AM +0200, Peter Zijlstra wrote: >> Furthermore, our hash function has definite room for improvement. > > After a bit of reading, using a 'strong' PRNG as base for a hash > function seems

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 4:06 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 11:36:59AM +0200, Peter Zijlstra wrote: >> Furthermore, our hash function has definite room for improvement. > > After a bit of reading, using a 'strong' PRNG as base for a hash > function seems generally suggested.

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Mon, Apr 4, 2016 at 8:14 AM, Doug Smythies <dsmyth...@telus.net> wrote: > On 2016.03.04 22:14 Sedat Dilek wrote: >> On Sun, Apr 3, 2016 at 8:59 PM, Doug Smythies <dsmyth...@telus.net> wrote: >>> On 2016.04.02 11:21 Sedat Dilek wrote: >>>> On Sa

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Mon, Apr 4, 2016 at 8:14 AM, Doug Smythies wrote: > On 2016.03.04 22:14 Sedat Dilek wrote: >> On Sun, Apr 3, 2016 at 8:59 PM, Doug Smythies wrote: >>> On 2016.04.02 11:21 Sedat Dilek wrote: >>>> On Sat, Apr 2, 2016 at 7:19 PM, Jörg Otte wrote: >>>

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Sun, Apr 3, 2016 at 8:59 PM, Doug Smythies <dsmyth...@telus.net> wrote: > On 2016.04.02 11:21 Sedat Dilek wrote: >> On Sat, Apr 2, 2016 at 7:19 PM, Jörg Otte wrote: >>> 2016-04-02 17:28 GMT+02:00 Srinivas Pandruvada wrote: >>>> Hi Doug, are you

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Sun, Apr 3, 2016 at 8:59 PM, Doug Smythies wrote: > On 2016.04.02 11:21 Sedat Dilek wrote: >> On Sat, Apr 2, 2016 at 7:19 PM, Jörg Otte wrote: >>> 2016-04-02 17:28 GMT+02:00 Srinivas Pandruvada wrote: >>>> Hi Doug, are you involved in the Ubuntu-OS? Develop

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Sat, Apr 2, 2016 at 7:19 PM, Jörg Otte <jrg.o...@gmail.com> wrote: > 2016-04-02 17:28 GMT+02:00 Srinivas Pandruvada > <srinivas.pandruv...@linux.intel.com>: >> >> On Sat, 2016-04-02 at 08:30 +0200, Sedat Dilek wrote: >>> > I am trying CPU_FREQ_DEFAULT

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Sat, Apr 2, 2016 at 7:19 PM, Jörg Otte wrote: > 2016-04-02 17:28 GMT+02:00 Srinivas Pandruvada > : >> >> On Sat, 2016-04-02 at 08:30 +0200, Sedat Dilek wrote: >>> > I am trying CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y from >>> > linux-pm.git#linux-next o

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Wed, Mar 30, 2016 at 8:47 PM, Tejun Heo wrote: > Hello, > > On Mon, Mar 28, 2016 at 09:45:53PM +0200, Miklos Szeredi wrote: >> >> commit 947e9762a8ddefda38aa21e249e6a4fec215cd12 >> >> Author: Tejun Heo >> >> Date: Fri May 22 18:23:32 2015 -0400 >> >> >> >>

Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Wed, Mar 30, 2016 at 8:47 PM, Tejun Heo wrote: > Hello, > > On Mon, Mar 28, 2016 at 09:45:53PM +0200, Miklos Szeredi wrote: >> >> commit 947e9762a8ddefda38aa21e249e6a4fec215cd12 >> >> Author: Tejun Heo >> >> Date: Fri May 22 18:23:32 2015 -0400 >> >> >> >> writeback: update

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Thu, Mar 31, 2016 at 5:42 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 05:59:54PM +0800, Boqun Feng wrote: >> So we should use macro like current_hardirq_context() here? Or >> considering the two helpers introduced in my RFC: >> >>

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Thu, Mar 31, 2016 at 5:42 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 05:59:54PM +0800, Boqun Feng wrote: >> So we should use macro like current_hardirq_context() here? Or >> considering the two helpers introduced in my RFC: >> >>

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 4:30 PM, Doug Smythies <dsmyth...@telus.net> wrote: > On 2016.03.31 01:11 Sedat Dilek wrote: >> On Thu, Mar 31, 2016 at 12:50 AM, Doug Smythies <dsmyth...@telus.net> wrote: >>> On 2106.03.30 15:19 Srinivas Pandruvada wrote: >>

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 4:30 PM, Doug Smythies wrote: > On 2016.03.31 01:11 Sedat Dilek wrote: >> On Thu, Mar 31, 2016 at 12:50 AM, Doug Smythies wrote: >>> On 2106.03.30 15:19 Srinivas Pandruvada wrote: >>>>> >>>>> Please see attached files. &

[tip.git#x86/debug] Re: x86/dumpstack: Combine some printk()s

Hi, I was looking through tip Git tree... Why didn't you use... + IS_ENABLED(CONFIG_DEBUG_PAGEALLOC) ? " DEBUG_PAGEALLOC" : "", ...instead of... + debug_pagealloc_enabled() ? " DEBUG_PAGEALLOC" : "", ...for consistency reasons? Regards, - Sedat - [1]

[tip.git#x86/debug] Re: x86/dumpstack: Combine some printk()s

Hi, I was looking through tip Git tree... Why didn't you use... + IS_ENABLED(CONFIG_DEBUG_PAGEALLOC) ? " DEBUG_PAGEALLOC" : "", ...instead of... + debug_pagealloc_enabled() ? " DEBUG_PAGEALLOC" : "", ...for consistency reasons? Regards, - Sedat - [1]

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 12:50 AM, Doug Smythies wrote: > On 2106.03.30 15:19 Srinivas Pandruvada wrote: >>> >>> Please see attached files. >>> >> Thanks. Your logs make sense. You have config set to performance mode >> by default (Which I believe default in all kernel

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 12:50 AM, Doug Smythies wrote: > On 2106.03.30 15:19 Srinivas Pandruvada wrote: >>> >>> Please see attached files. >>> >> Thanks. Your logs make sense. You have config set to performance mode >> by default (Which I believe default in all kernel Ubuntu). > > Yes, but via a

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 1:41 AM, Rafael J. Wysocki <raf...@kernel.org> wrote: > On Thu, Mar 31, 2016 at 1:32 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> On Thu, Mar 31, 2016 at 1:28 AM, Rafael J. Wysocki <raf...@kernel.org> wrote: >>> On Thu, Mar 31, 20

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 1:41 AM, Rafael J. Wysocki wrote: > On Thu, Mar 31, 2016 at 1:32 AM, Sedat Dilek wrote: >> On Thu, Mar 31, 2016 at 1:28 AM, Rafael J. Wysocki wrote: >>> On Thu, Mar 31, 2016 at 1:25 AM, Sedat Dilek wrote: >>>> On Thu, Mar 31, 2016 at

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 1:28 AM, Rafael J. Wysocki <raf...@kernel.org> wrote: > On Thu, Mar 31, 2016 at 1:25 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> On Thu, Mar 31, 2016 at 1:17 AM, Pandruvada, Srinivas >> <srinivas.pandruv...@intel.com> wrote: >

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Thu, Mar 31, 2016 at 1:28 AM, Rafael J. Wysocki wrote: > On Thu, Mar 31, 2016 at 1:25 AM, Sedat Dilek wrote: >> On Thu, Mar 31, 2016 at 1:17 AM, Pandruvada, Srinivas >> wrote: >>> On Wed, 2016-03-30 at 15:46 -0700, Srinivas Pandruvada wrote: >>>> On Thu,

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Wed, Mar 30, 2016 at 11:58 PM, Rafael J. Wysocki <rafael.j.wyso...@intel.com> wrote: > On 3/30/2016 11:41 PM, Sedat Dilek wrote: >> >> Hi, >> >> I am using Intel-PState-Driver here with v4.6-rc1 and >> Intel-SandyBridge-CPU. >> >> Here are m

Re: [intel-pstate driver regression] processor frequency very high even if in idle

On Wed, Mar 30, 2016 at 11:58 PM, Rafael J. Wysocki wrote: > On 3/30/2016 11:41 PM, Sedat Dilek wrote: >> >> Hi, >> >> I am using Intel-PState-Driver here with v4.6-rc1 and >> Intel-SandyBridge-CPU. >> >> Here are my turbostat results attached. >

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 4:06 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 11:36:59AM +0200, Peter Zijlstra wrote: >> Furthermore, our hash function has definite room for improvement. > > After a bit of reading, using a 'strong' PRNG as base for a hash > function seems

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 4:06 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 11:36:59AM +0200, Peter Zijlstra wrote: >> Furthermore, our hash function has definite room for improvement. > > After a bit of reading, using a 'strong' PRNG as base for a hash > function seems generally suggested.

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 2:43 PM, Peter Zijlstra <pet...@infradead.org> wrote: > On Wed, Mar 30, 2016 at 11:49:57AM +0200, Sedat Dilek wrote: >> On Wed, Mar 30, 2016 at 11:36 AM, Peter Zijlstra <pet...@infradead.org> >> wrote: > >> > OK, so while the code

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 2:43 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 11:49:57AM +0200, Sedat Dilek wrote: >> On Wed, Mar 30, 2016 at 11:36 AM, Peter Zijlstra >> wrote: > >> > OK, so while the code in check_no_collision() seems sensible, it

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 12:36 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 05:59:54PM +0800, Boqun Feng wrote: >> > @@ -3164,6 +3181,7 @@ static int __lock_acquire(struct lockdep_map *lock, >> > unsigned int subclass, >> > hlock->acquire_ip = ip; >> >

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 12:36 PM, Peter Zijlstra wrote: > On Wed, Mar 30, 2016 at 05:59:54PM +0800, Boqun Feng wrote: >> > @@ -3164,6 +3181,7 @@ static int __lock_acquire(struct lockdep_map *lock, >> > unsigned int subclass, >> > hlock->acquire_ip = ip; >> > hlock->instance = lock; >> >

[tip:core/urgent] tools/lib/lockdep: Fix unsupported 'basename -s' in run_tests.sh

Commit-ID: a189c017ded0f13650793067fb7a1afbc2b98cd5 Gitweb: http://git.kernel.org/tip/a189c017ded0f13650793067fb7a1afbc2b98cd5 Author: Sedat Dilek <sedat.di...@gmail.com> AuthorDate: Wed, 30 Mar 2016 10:22:49 +0200 Committer: Ingo Molnar <mi...@kernel.org> CommitDate: Wed, 30

[tip:core/urgent] tools/lib/lockdep: Fix unsupported 'basename -s' in run_tests.sh

Commit-ID: a189c017ded0f13650793067fb7a1afbc2b98cd5 Gitweb: http://git.kernel.org/tip/a189c017ded0f13650793067fb7a1afbc2b98cd5 Author: Sedat Dilek AuthorDate: Wed, 30 Mar 2016 10:22:49 +0200 Committer: Ingo Molnar CommitDate: Wed, 30 Mar 2016 12:45:56 +0200 tools/lib/lockdep: Fix

Re: [PATCH RESEND] mwifiex: fix NULL pointer dereference error

On Wed, Mar 30, 2016 at 12:38 PM, Wei-Ning Huang <wnhu...@google.com> wrote: > ah.. thanks. > > Kalle, can you help amend the message if this patch is accepted? > Thanks a lot. > http://its-not-its.info/ - Sedat - > Wei-Ning > > On Wed, Mar 30, 2016 at

Re: [PATCH RESEND] mwifiex: fix NULL pointer dereference error

On Wed, Mar 30, 2016 at 12:38 PM, Wei-Ning Huang wrote: > ah.. thanks. > > Kalle, can you help amend the message if this patch is accepted? > Thanks a lot. > http://its-not-its.info/ - Sedat - > Wei-Ning > > On Wed, Mar 30, 2016 at 6:26 PM, Sedat Dilek wrote: >>

Re: [PATCH RESEND] mwifiex: fix NULL pointer dereference error

On Wed, Mar 30, 2016 at 12:14 PM, Wei-Ning Huang wrote: > In mwifiex_enable_hs, we need to check if > priv->wdev.wiphy->wowlan_config is NULL before accessing it's member. it's... its member (not it's) :-). - Sedat - > This sometimes cause kernel panic when

Re: [PATCH RESEND] mwifiex: fix NULL pointer dereference error

On Wed, Mar 30, 2016 at 12:14 PM, Wei-Ning Huang wrote: > In mwifiex_enable_hs, we need to check if > priv->wdev.wiphy->wowlan_config is NULL before accessing it's member. it's... its member (not it's) :-). - Sedat - > This sometimes cause kernel panic when suspend/resume. > > Signed-off-by:

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 11:36 AM, Peter Zijlstra wrote: > On Tue, Mar 29, 2016 at 10:47:02AM +0200, Ingo Molnar wrote: > >> > You are right; this is lockdep running into a hash collision; which is a >> > new >> > DEBUG_LOCKDEP test. See 9e4e7554e755 ("locking/lockdep:

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Wed, Mar 30, 2016 at 11:36 AM, Peter Zijlstra wrote: > On Tue, Mar 29, 2016 at 10:47:02AM +0200, Ingo Molnar wrote: > >> > You are right; this is lockdep running into a hash collision; which is a >> > new >> > DEBUG_LOCKDEP test. See 9e4e7554e755 ("locking/lockdep: Detect chain_key >> >

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

> [0.00] --- > [0.00] Good, all 253 testcases passed! | > [0.00] - > > And it's all good? > ( On shutdown I saw an(other) issue - will investigate, might not be related. > ) > The initial

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

> [0.00] --- > [0.00] Good, all 253 testcases passed! | > [0.00] - > > And it's all good? > ( On shutdown I saw an(other) issue - will investigate, might not be related. > ) > The initial

[PATCH] liblockdep: Fix unsupported 'basename -s' in run_tests.sh

<torva...@linux-foundation.org> Cc: Ingo Molnar <mi...@kernel.org> Cc: Theodore Ts'o <ty...@mit.edu> Cc: Boqun Feng <boqun.f...@gmail.com> Cc: LKML <linux-kernel@vger.kernel.org> Cc: linux-fsdevel <linux-fsde...@vger.kernel.org> Signed-off-by: Sedat Dilek <

[PATCH] liblockdep: Fix unsupported 'basename -s' in run_tests.sh

Cc: Boqun Feng Cc: LKML Cc: linux-fsdevel Signed-off-by: Sedat Dilek --- tools/lib/lockdep/run_tests.sh | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/tools/lib/lockdep/run_tests.sh b/tools/lib/lockdep/run_tests.sh index 5334ad9d39b7..1069d96248c1 100755

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 10:59 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Sun, Mar 27, 2016 at 10:48 PM, Peter Zijlstra <pet...@infradead.org> wrote: >> On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: >>> Anyway, I don't think that DEBUG_LOCKS

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 10:59 PM, Sedat Dilek wrote: > On Sun, Mar 27, 2016 at 10:48 PM, Peter Zijlstra wrote: >> On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: >>> Anyway, I don't think that DEBUG_LOCKS_WARN_ON() in >>> >>> kernel/l

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 10:48 PM, Peter Zijlstra wrote: > On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: >> Anyway, I don't think that DEBUG_LOCKS_WARN_ON() in >> >> kernel/locking/lockdep.c:2017 __lock_acquire >> >> would be an ext4 issue, it looks more

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 10:48 PM, Peter Zijlstra wrote: > On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: >> Anyway, I don't think that DEBUG_LOCKS_WARN_ON() in >> >> kernel/locking/lockdep.c:2017 __lock_acquire >> >> would be an ext4 issue, it looks more like an internal

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 9:42 PM, Linus Torvalds <torva...@linux-foundation.org> wrote: > > On Mar 27, 2016 14:40, "Sedat Dilek" <sedat.di...@gmail.com> wrote: >> >> So far I can say, that I am *not* seeing this with ext4.git#dev on top >> of v4.6-rc1

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 9:42 PM, Linus Torvalds wrote: > > On Mar 27, 2016 14:40, "Sedat Dilek" wrote: >> >> So far I can say, that I am *not* seeing this with ext4.git#dev on top >> of v4.6-rc1. > > Mind re-testing just plain 4.6-rc1 again? It might not h

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 8:23 PM, Theodore Ts'o wrote: > On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: >> >> Unless you're using overlayfs or per-file encryption, I'm not seeing >> that any of that should make any difference (but it's entirely >> possible I'm

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 8:23 PM, Theodore Ts'o wrote: > On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: >> >> Unless you're using overlayfs or per-file encryption, I'm not seeing >> that any of that should make any difference (but it's entirely >> possible I'm missing something).

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:33 AM, Miklos Szeredi <mik...@szeredi.hu> wrote: > On Thu, Mar 17, 2016 at 10:09 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >> On Thu, Mar 17, 2016 at 10:02 AM, Miklos Szeredi <mik...@szeredi.hu> wrote: >>> From:

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:33 AM, Miklos Szeredi wrote: > On Thu, Mar 17, 2016 at 10:09 AM, Sedat Dilek wrote: >> On Thu, Mar 17, 2016 at 10:02 AM, Miklos Szeredi wrote: >>> From: Miklos Szeredi >>> >>> This series fixes bugs in nfs and ext4 due to 4bacc

Re: linux-next: Tree for Feb 24

On Wed, Feb 24, 2016 at 3:37 PM, Benjamin LaHaise <b...@kvack.org> wrote: > On Wed, Feb 24, 2016 at 07:32:17AM +0100, Sedat Dilek wrote: >> On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell <s...@canb.auug.org.au> >> wrote: >> > Hi all, >> > >>

Re: linux-next: Tree for Feb 24

On Wed, Feb 24, 2016 at 3:37 PM, Benjamin LaHaise wrote: > On Wed, Feb 24, 2016 at 07:32:17AM +0100, Sedat Dilek wrote: >> On Wed, Feb 24, 2016 at 6:34 AM, Stephen Rothwell >> wrote: >> > Hi all, >> > >> > Changes since 20160223: >> > >>

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:02 AM, Miklos Szeredi wrote: > From: Miklos Szeredi > > This series fixes bugs in nfs and ext4 due to 4bacc9c9234c ("overlayfs: Make > f_path always point to the overlay and f_inode to the underlay"). > Can you put that series

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 10:02 AM, Miklos Szeredi wrote: > From: Miklos Szeredi > > This series fixes bugs in nfs and ext4 due to 4bacc9c9234c ("overlayfs: Make > f_path always point to the overlay and f_inode to the underlay"). > Can you put that series in your vfs.git tree? Easier for getting

Re: linux-next: Tree for Feb 24

On Thu, Mar 17, 2016 at 11:27 AM, Stephen Rothwell <s...@canb.auug.org.au> wrote: > Hi Sedat, > > On Thu, 17 Mar 2016 11:21:56 +0100 Sedat Dilek <sedat.di...@gmail.com> wrote: >> >> not seeing this anymore. >> How was that solved? > > The cod

Re: linux-next: Tree for Feb 24

On Thu, Mar 17, 2016 at 11:27 AM, Stephen Rothwell wrote: > Hi Sedat, > > On Thu, 17 Mar 2016 11:21:56 +0100 Sedat Dilek wrote: >> >> not seeing this anymore. >> How was that solved? > > The code has been removed while it is further worked on and revie

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 11:15 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Thu, Mar 17, 2016 at 10:33 AM, Miklos Szeredi <mik...@szeredi.hu> wrote: >> On Thu, Mar 17, 2016 at 10:09 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: >>> On Thu, Mar 17, 2

Re: [PATCH 1/4] vfs: add file_dentry()

On Thu, Mar 17, 2016 at 11:15 AM, Sedat Dilek wrote: > On Thu, Mar 17, 2016 at 10:33 AM, Miklos Szeredi wrote: >> On Thu, Mar 17, 2016 at 10:09 AM, Sedat Dilek wrote: >>> On Thu, Mar 17, 2016 at 10:02 AM, Miklos Szeredi wrote: >>>> From: Miklos Szeredi >>&

Re: [PATCH 4.4 00/74] 4.4.5-stable review

On Sun, Mar 13, 2016 at 4:45 AM, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Tue, Mar 08, 2016 at 05:15:13PM +0100, Sedat Dilek wrote: >> On Tue, Mar 8, 2016 at 2:39 PM, Greg Kroah-Hartman >> <gre...@linuxfoundation.org> wrote: >> > On Tue, Mar

Re: [PATCH 4.4 00/74] 4.4.5-stable review

On Sun, Mar 13, 2016 at 4:45 AM, Greg Kroah-Hartman wrote: > On Tue, Mar 08, 2016 at 05:15:13PM +0100, Sedat Dilek wrote: >> On Tue, Mar 8, 2016 at 2:39 PM, Greg Kroah-Hartman >> wrote: >> > On Tue, Mar 08, 2016 at 10:12:13AM +0100, Sedat Dilek wrote: >> >> H

Re: [PATCH 4.4 00/74] 4.4.5-stable review

On Tue, Mar 8, 2016 at 2:39 PM, Greg Kroah-Hartman <gre...@linuxfoundation.org> wrote: > On Tue, Mar 08, 2016 at 10:12:13AM +0100, Sedat Dilek wrote: >> Hi Greg, >> >> I tested with my usual setup/config. >> >> Looks good so far. >> >> Missing

Re: [PATCH 4.4 00/74] 4.4.5-stable review

On Tue, Mar 8, 2016 at 2:39 PM, Greg Kroah-Hartman wrote: > On Tue, Mar 08, 2016 at 10:12:13AM +0100, Sedat Dilek wrote: >> Hi Greg, >> >> I tested with my usual setup/config. >> >> Looks good so far. >> >> Missing some net-ppp-fixes / overlayfs-

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Mon, Mar 7, 2016 at 5:41 PM, Alan Stern <st...@rowland.harvard.edu> wrote: > On Mon, 7 Mar 2016, Sedat Dilek wrote: > >> Hmm, we are there where I was looking at... >> >> Please, read the reply of Jiri [1], we did some tweaking. >> With CONFIG_FTRACE=n and CO

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Mon, Mar 7, 2016 at 5:41 PM, Alan Stern wrote: > On Mon, 7 Mar 2016, Sedat Dilek wrote: > >> Hmm, we are there where I was looking at... >> >> Please, read the reply of Jiri [1], we did some tweaking. >> With CONFIG_FTRACE=n and CONFIG_PROVE_LOCKING=n ! > >

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Mon, Mar 7, 2016 at 6:05 PM, Jiri Kosina wrote: > On Mon, 7 Mar 2016, Alan Stern wrote: > >> > 319: 9c pushfq >> > 31a: 41 5c pop%r12 >> > 31c: 48 89 dfmov%rbx,%rdi >> > 31f:

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Mon, Mar 7, 2016 at 6:05 PM, Jiri Kosina wrote: > On Mon, 7 Mar 2016, Alan Stern wrote: > >> > 319: 9c pushfq >> > 31a: 41 5c pop%r12 >> > 31c: 48 89 dfmov%rbx,%rdi >> > 31f: e8 00 00 00

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Mon, Mar 7, 2016 at 4:59 PM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Sun, Mar 6, 2016 at 6:23 PM, Alan Stern <st...@rowland.harvard.edu> wrote: >> On Sat, 5 Mar 2016, Sedat Dilek wrote: >> >>> On Fri, Mar 4, 2016 at 5:04 PM, Alan Stern &l

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Mon, Mar 7, 2016 at 4:59 PM, Sedat Dilek wrote: > On Sun, Mar 6, 2016 at 6:23 PM, Alan Stern wrote: >> On Sat, 5 Mar 2016, Sedat Dilek wrote: >> >>> On Fri, Mar 4, 2016 at 5:04 PM, Alan Stern >>> wrote: >>> > On Wed, 2 Mar 2016, Sedat Dilek wro

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Sun, Mar 6, 2016 at 6:23 PM, Alan Stern <st...@rowland.harvard.edu> wrote: > On Sat, 5 Mar 2016, Sedat Dilek wrote: > >> On Fri, Mar 4, 2016 at 5:04 PM, Alan Stern <st...@rowland.harvard.edu> wrote: >> > On Wed, 2 Mar 2016, Sedat Dilek wrote: >

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On Sun, Mar 6, 2016 at 6:23 PM, Alan Stern wrote: > On Sat, 5 Mar 2016, Sedat Dilek wrote: > >> On Fri, Mar 4, 2016 at 5:04 PM, Alan Stern wrote: >> > On Wed, 2 Mar 2016, Sedat Dilek wrote: >> > >> >> On 3/1/16, Alan Stern wrote: >

Re: [PATCH] ovl: copy new uid/gid into overlayfs runtime inode

On 3/3/16, Miklos Szeredi wrote: > On Sun, Jan 31, 2016 at 2:21 PM, Konstantin Khlebnikov > wrote: >> Overlayfs must update uid/gid after chown, otherwise functions >> like inode_owner_or_capable() will check user against stale uid. >> Catched by xfstests

<    3   4   5   6   7   8   9   10   11   12   >