[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1219113549.8062.13.camel@pasglop>
Date: Tue, 19 Aug 2008 12:39:09 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Scott Wood <scottwood@...escale.com>,
Eran Liberty <liberty@...ricom.com>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
Steven Rostedt <srostedt@...hat.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: ftrace introduces instability into kernel 2.6.27(-rc2,-rc3)
> Hmm, this was originally copied from x86, where we did a cmpxchg, but that
> is probably not needed since all of this is done in kstop_machine. Also,
> only the "get" is needed. If we don't fault there, we wont fault on the
> put (unless we have permissions wrong, and that would be a bug).
Would it ? How do we make sure the kernel text is mapped writeable ?
> So are you recommending something like
>
> int cmd;
>
> if (__get_user(cmd, ip))
> goto fault;
>
> if (cmd != old)
> goto not_same;
>
> WARN_ON_ONCE(__put_user(cmd, ip));
>
> If we did this, we could probably put this into the generic code:
That would work I suppose, I'll give it a try.
> if (copy_from_user(cmd, ip, ARCH_CALL_SIZE))
> goto fault;
>
> if (memcmp(cmd, old, ARCH_CALL_SIZE) != 0)
> goto not_same;
>
> WARN_ON_ONCE(copy_to_user(cmd, ip, ARCH_CALL_SIZE));
You need the __ variants or the access_ok() checks will bite
you bad.
Ben.
--
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