Thread (18 messages) 18 messages, 7 authors, 2018-09-06

Re: [PATCH 05/11] UAPI: coda: Don't use internal kernel structs in UAPI

From: Jan Harkes <jaharkes@cs.cmu.edu>
Date: 2018-09-05 21:56:20
Also in: linux-api, linux-kbuild, lkml

On Wed, Sep 05, 2018 at 04:55:10PM +0100, David Howells wrote:
The size and layout of internal kernel structures may not be relied upon
outside of the kernel and may even change in a containerised environment if
a container image is frozen and shifted to another machine.

Excise these from Coda's upc_req struct.
Argh, that won't work.

I still have to look at where this structure is used exactly, but...

Either this structure is used by the messages that the kernel sends to
userspace, in which case we don't want the kernel to pack the larger
structure that includes a list_head and a wait_queue_head_t in the
message while userspace reads as if it was a smaller structure without
those.

But my gut feeling is that this is not part of the upcall request
messages and never gets to userspace and as such shouldn't be in uapi to
begin with.

Jan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help