[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141028020224.GA28581@redhat.com>
Date: Tue, 28 Oct 2014 03:02:24 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc: Davidlohr Bueso <dave@...olabs.net>, akpm@...ux-foundation.org,
hughd@...gle.com, riel@...hat.com, mgorman@...e.de,
peterz@...radead.org, mingo@...nel.org,
linux-kernel@...r.kernel.org, dbueso@...e.de, linux-mm@...ck.org
Subject: Re: [PATCH 05/10] uprobes: share the i_mmap_rwsem
On 10/27, Srikar Dronamraju wrote:
>
> Copying Oleg (since he should have been copied on this one)
Thanks ;)
> Please see one comment below.
>
> Acked-by: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
>
> > ---
> > kernel/events/uprobes.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
> > index 045b649..7a9e620 100644
> > --- a/kernel/events/uprobes.c
> > +++ b/kernel/events/uprobes.c
> > @@ -724,7 +724,7 @@ build_map_info(struct address_space *mapping, loff_t offset, bool is_register)
> > int more = 0;
> >
> > again:
> > - i_mmap_lock_write(mapping);
> > + i_mmap_lock_read(mapping);
I too think the patch is fine.
I didn't see other changes, but I hope that i_mmap_lock_write/read names
provide enough info and ->i_mmap_mutex was turned into rw-lock, in this
case read-lock should be enough.
Oleg.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists