On Mon, Nov 10, 2014 at 12:20:20AM -0500, David Miller wrote: > From: Al Viro <v...@zeniv.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.
Sure, but why do we have access_ok() there at all? I.e. why not just have it constant 1? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
