[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANZNk83dJCXAWrQ+i5rh=sdUuiiD5ZhzDua-rjJpBZCzzNGDJA@mail.gmail.com>
Date: Sat, 19 Jul 2014 00:06:28 +0300
From: Andrey Utkin <andrey.krieger.utkin@...il.com>
To: Julian Anastasov <ja@....bg>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org, coreteam@...filter.org,
netfilter-devel@...r.kernel.org, lvs-devel@...r.kernel.org,
netdev@...r.kernel.org, dcb314@...mail.com,
David Miller <davem@...emloft.net>, kadlec@...ckhole.kfki.hu,
Patrick McHardy <kaber@...sh.net>, pablo@...filter.org,
Simon Horman <horms@...ge.net.au>, wensong@...ux-vs.org
Subject: Re: [PATCH 3/5] net/netfilter/ipvs/ip_vs_ctl.c: drop argument range
check just before the check for equality
2014-07-18 23:48 GMT+03:00 Julian Anastasov <ja@....bg>:
> The above check ensures the set_arglen[] value (some
> struct size) does not exceed the arg[MAX_ARG_LEN] space. You can check
> commit 04bcef2a83f40c ("ipvs: Add boundary check on ioctl arguments")
> for more info.
Thanks for info.
What about static check at compilation time?
#if (DAEMON_ARG_LEN > MAX_ARG_LEN) \
|| (SERVICE_ARG_LEN > MAX_ARG_LEN) \
|| (SVCDEST_ARG_LEN > MAX_ARG_LEN)
#error MAX_ARG_LEN exceeded in set_arglen table
#endif
--
Andrey Utkin
--
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