[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101112173400.GA8659@redhat.com>
Date: Fri, 12 Nov 2010 18:34:00 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Greg Thelen <gthelen@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Jens Axboe <axboe@...nel.dk>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] ioprio: grab rcu_read_lock in sys_ioprio_{set,get}()
On 11/11, Greg Thelen wrote:
>
> The fix is to:
> a) grab rcu lock in sys_ioprio_{set,get}() and
> b) avoid grabbing tasklist_lock.
> Discussion in: http://marc.info/?l=linux-kernel&m=128951324702889
>
> Signed-off-by: Greg Thelen <gthelen@...gle.com>
Reviewed-by: Oleg Nesterov <oleg@...hat.com>
> ---
> fs/ioprio.c | 13 ++++---------
> 1 files changed, 4 insertions(+), 9 deletions(-)
>
> diff --git a/fs/ioprio.c b/fs/ioprio.c
> index 748cfb9..7da2a06 100644
> --- a/fs/ioprio.c
> +++ b/fs/ioprio.c
> @@ -103,12 +103,7 @@ SYSCALL_DEFINE3(ioprio_set, int, which, int, who, int, ioprio)
> }
>
> ret = -ESRCH;
> - /*
> - * We want IOPRIO_WHO_PGRP/IOPRIO_WHO_USER to be "atomic",
> - * so we can't use rcu_read_lock(). See re-copy of ->ioprio
> - * in copy_process().
> - */
> - read_lock(&tasklist_lock);
> + rcu_read_lock();
> switch (which) {
> case IOPRIO_WHO_PROCESS:
> if (!who)
> @@ -153,7 +148,7 @@ free_uid:
> ret = -EINVAL;
> }
>
> - read_unlock(&tasklist_lock);
> + rcu_read_unlock();
> return ret;
> }
>
> @@ -197,7 +192,7 @@ SYSCALL_DEFINE2(ioprio_get, int, which, int, who)
> int ret = -ESRCH;
> int tmpio;
>
> - read_lock(&tasklist_lock);
> + rcu_read_lock();
> switch (which) {
> case IOPRIO_WHO_PROCESS:
> if (!who)
> @@ -250,6 +245,6 @@ SYSCALL_DEFINE2(ioprio_get, int, which, int, who)
> ret = -EINVAL;
> }
>
> - read_unlock(&tasklist_lock);
> + rcu_read_unlock();
> return ret;
> }
> --
> 1.7.3.1
>
--
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