[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB028519B@AcuExch.aculab.com>
Date: Mon, 13 Feb 2017 16:30:36 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Scott Bauer' <scott.bauer@...el.com>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>
CC: "arnd@...db.de" <arnd@...db.de>, "axboe@...com" <axboe@...com>,
"keith.busch@...el.com" <keith.busch@...el.com>,
"jonathan.derrick@...el.com" <jonathan.derrick@...el.com>,
"hch@...radead.org" <hch@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
Subject: RE: [PATCH V5 3/4] Move stack parameters for sed_ioctl to prevent
oversized stack with CONFIG_KASAN
From: Scott Bauer Sent: 13 February 2017 16:11
> When CONFIG_KASAN is enabled, compilation fails:
>
> block/sed-opal.c: In function 'sed_ioctl':
> block/sed-opal.c:2447:1: error: the frame size of 2256 bytes is larger than 2048 bytes [-Werror=frame-
> larger-than=]
>
> Moved all the ioctl structures off the stack and dynamically activate
> using _IOC_SIZE()
Think I'd not that this simplifies the code considerably.
AFAICT CONFIG_KASAN is a just brainf*ck.
It at least needs annotation that copy_from_user() has properties
similar to memset().
So if the size matches that of the type then no guard space (etc)
is required.
...
> + ioctl_ptr = memdup_user(arg, _IOC_SIZE(cmd));
> + if (IS_ERR_OR_NULL(ioctl_ptr)) {
> + ret = PTR_ERR(ioctl_ptr);
> + goto out;
...
> + out:
> + kfree(ioctl_ptr);
> + return ret;
> }
That error path doesn't look quite right to me.
David
Powered by blists - more mailing lists