Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Daniel Wagner
On 03/04/2015 10:01 PM, Jeff Layton wrote: I pulled down the most recent Fedora rawhide kernel today: 4.0.0-0.rc2.git0.1.fc23.x86_64 ...and with that, I can't reproduce this. The ftrace_event_field slab (which is shared by the fasync_struct cache) seems to stay under control. I see it

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 16:01:36 -0500 Jeff Layton wrote: > On Wed, 4 Mar 2015 15:20:33 +0100 > Daniel Wagner wrote: > > > On 03/03/2015 01:55 AM, Jeff Layton wrote: > > > On Mon, 2 Mar 2015 15:25:12 +0100 > > > Daniel Wagner wrote: > > > > > >> The locks_insert/delete_block() functions are used

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 15:20:33 +0100 Daniel Wagner wrote: > On 03/03/2015 01:55 AM, Jeff Layton wrote: > > On Mon, 2 Mar 2015 15:25:12 +0100 > > Daniel Wagner wrote: > > > >> The locks_insert/delete_block() functions are used for flock, posix > >> and leases types. blocked_lock_lock is used to

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 12:59:23 -0500 Jeff Layton wrote: > On Wed, 4 Mar 2015 16:32:57 +0100 > Daniel Wagner wrote: > > > On 03/04/2015 04:00 PM, Boaz Harrosh wrote: > > > On 03/04/2015 04:20 PM, Daniel Wagner wrote: > > >> On 03/03/2015 01:55 AM, Jeff Layton wrote: > > >>> On Mon, 2 Mar 2015

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 16:32:57 +0100 Daniel Wagner wrote: > On 03/04/2015 04:00 PM, Boaz Harrosh wrote: > > On 03/04/2015 04:20 PM, Daniel Wagner wrote: > >> On 03/03/2015 01:55 AM, Jeff Layton wrote: > >>> On Mon, 2 Mar 2015 15:25:12 +0100 > >>> Daniel Wagner wrote: > >>> > > <> > >> I have

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Daniel Wagner
On 03/04/2015 04:00 PM, Boaz Harrosh wrote: > On 03/04/2015 04:20 PM, Daniel Wagner wrote: >> On 03/03/2015 01:55 AM, Jeff Layton wrote: >>> On Mon, 2 Mar 2015 15:25:12 +0100 >>> Daniel Wagner wrote: >>> > <> >> I have fixed that stuff and now I am testing it. Though it seems >> that there is a

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Boaz Harrosh
On 03/04/2015 04:20 PM, Daniel Wagner wrote: > On 03/03/2015 01:55 AM, Jeff Layton wrote: >> On Mon, 2 Mar 2015 15:25:12 +0100 >> Daniel Wagner wrote: >> <> > I have fixed that stuff and now I am testing it. Though it seems > that there is a memory leak which can be triggered with > >

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Daniel Wagner
On 03/03/2015 01:55 AM, Jeff Layton wrote: > On Mon, 2 Mar 2015 15:25:12 +0100 > Daniel Wagner wrote: > >> The locks_insert/delete_block() functions are used for flock, posix >> and leases types. blocked_lock_lock is used to serialize all access to >> fl_link, fl_block, fl_next and

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Daniel Wagner
On 03/04/2015 04:00 PM, Boaz Harrosh wrote: On 03/04/2015 04:20 PM, Daniel Wagner wrote: On 03/03/2015 01:55 AM, Jeff Layton wrote: On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: I have fixed that stuff and now I am testing it. Though it seems that

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 16:32:57 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: On 03/04/2015 04:00 PM, Boaz Harrosh wrote: On 03/04/2015 04:20 PM, Daniel Wagner wrote: On 03/03/2015 01:55 AM, Jeff Layton wrote: On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 12:59:23 -0500 Jeff Layton jlay...@poochiereds.net wrote: On Wed, 4 Mar 2015 16:32:57 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: On 03/04/2015 04:00 PM, Boaz Harrosh wrote: On 03/04/2015 04:20 PM, Daniel Wagner wrote: On 03/03/2015 01:55 AM, Jeff Layton

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 15:20:33 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: On 03/03/2015 01:55 AM, Jeff Layton wrote: On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: The locks_insert/delete_block() functions are used for flock, posix and

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Jeff Layton
On Wed, 4 Mar 2015 16:01:36 -0500 Jeff Layton jlay...@poochiereds.net wrote: On Wed, 4 Mar 2015 15:20:33 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: On 03/03/2015 01:55 AM, Jeff Layton wrote: On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote:

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Daniel Wagner
On 03/04/2015 10:01 PM, Jeff Layton wrote: I pulled down the most recent Fedora rawhide kernel today: 4.0.0-0.rc2.git0.1.fc23.x86_64 ...and with that, I can't reproduce this. The ftrace_event_field slab (which is shared by the fasync_struct cache) seems to stay under control. I see it

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Daniel Wagner
On 03/03/2015 01:55 AM, Jeff Layton wrote: On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: The locks_insert/delete_block() functions are used for flock, posix and leases types. blocked_lock_lock is used to serialize all access to fl_link, fl_block, fl_next

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-04 Thread Boaz Harrosh
On 03/04/2015 04:20 PM, Daniel Wagner wrote: On 03/03/2015 01:55 AM, Jeff Layton wrote: On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: I have fixed that stuff and now I am testing it. Though it seems that there is a memory leak which can be triggered with

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-02 Thread Jeff Layton
On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner wrote: > The locks_insert/delete_block() functions are used for flock, posix > and leases types. blocked_lock_lock is used to serialize all access to > fl_link, fl_block, fl_next and blocked_hash. Here, we prepare the > stage for using

[RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-02 Thread Daniel Wagner
The locks_insert/delete_block() functions are used for flock, posix and leases types. blocked_lock_lock is used to serialize all access to fl_link, fl_block, fl_next and blocked_hash. Here, we prepare the stage for using blocked_lock_lock to protect blocked_hash. Signed-off-by: Daniel Wagner Cc:

Re: [RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-02 Thread Jeff Layton
On Mon, 2 Mar 2015 15:25:12 +0100 Daniel Wagner daniel.wag...@bmw-carit.de wrote: The locks_insert/delete_block() functions are used for flock, posix and leases types. blocked_lock_lock is used to serialize all access to fl_link, fl_block, fl_next and blocked_hash. Here, we prepare the stage

[RFC v2 3/4] locks: Split insert/delete block functions into flock/posix parts

2015-03-02 Thread Daniel Wagner
The locks_insert/delete_block() functions are used for flock, posix and leases types. blocked_lock_lock is used to serialize all access to fl_link, fl_block, fl_next and blocked_hash. Here, we prepare the stage for using blocked_lock_lock to protect blocked_hash. Signed-off-by: Daniel Wagner