[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090424143446.GA6849@redhat.com>
Date: Fri, 24 Apr 2009 16:34:46 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Hugh Dickins <hugh@...itas.com>
Cc: Al Viro <viro@...IV.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Joe Malicki <jmalicki@...acarta.com>,
Michael Itz <mitz@...acarta.com>,
Kenneth Baker <bakerk@...acarta.com>,
Chris Wright <chrisw@...s-sol.org>,
David Howells <dhowells@...hat.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Roland McGrath <roland@...hat.com>
Subject: Re: [PATCH 3/2] check_unsafe_exec: rcu_read_unlock
On 04/24, Hugh Dickins wrote:
>
> --- 2.6.30-rc3-next-20090424/fs/exec.c 2009-04-24 12:23:43.000000000 +0100
> +++ linux/fs/exec.c 2009-04-24 12:26:10.000000000 +0100
> @@ -1043,7 +1043,7 @@ int check_unsafe_exec(struct linux_binpr
> if (t->fs == p->fs)
> n_fs++;
> }
> - rcu_read_lock();
> + rcu_read_unlock();
I'd say this change is not bad. Except it discloses the fact I didn't
bother to test my trivial patch.
Thanks a lot Hugh!!!
And my apologies to all.
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