[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20141110.002020.1062493586889118565.davem@davemloft.net>
Date: Mon, 10 Nov 2014 00:20:20 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: viro@...IV.linux.org.uk
Cc: herbert@...dor.apana.org.au, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, bcrl@...ck.org, mst@...hat.com
Subject: Re: [PATCH 1/4] inet: Add skb_copy_datagram_iter
From: Al Viro <viro@...IV.linux.org.uk>
Date: Sun, 9 Nov 2014 21:19:08 +0000
> 1) does sparc64 access_ok() need to differ for 32bit and 64bit tasks?
sparc64 will just fault no matter what kind of task it is.
It is impossible for a user task to generate a reference to
a kernel virtual address, as kernel and user accesses each
go via a separate address space identifier.
--
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