[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161123103352.6c2afaf2@gandalf.local.home>
Date: Wed, 23 Nov 2016 10:33:52 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: alexander.levin@...izon.com
Cc: "dvyukov@...gle.com" <dvyukov@...gle.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"scientist@...com" <scientist@...com>,
"glider@...gle.com" <glider@...gle.com>,
"andreyknvl@...gle.com" <andreyknvl@...gle.com>,
"arnd@...db.de" <arnd@...db.de>,
"mathieu.desnoyers@...icios.com" <mathieu.desnoyers@...icios.com>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 1/3] abi_spec: basic definitions of constraints, args and
syscalls
On Wed, 23 Nov 2016 15:03:23 +0000
alexander.levin@...izon.com wrote:
> - This should also work for ioctls in the future.
Any ioctl that requires more than 6 arguments should also be NACKed in
the future. If you need that many arguments, its best to simply create
a structure and pass that it.
Again, the function syscalls_get_arguments() will BUG() on most archs
if it expects more than 6 arguments.
-- Steve
Powered by blists - more mailing lists