[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJZ-BfJPA+m1BOuVVQxPb8SXpSRo+F2cVTF62C9JTyRXQ@mail.gmail.com>
Date: Sun, 26 Aug 2018 14:56:47 -0700
From: Kees Cook <keescook@...omium.org>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Al Viro <viro@...iv.linux.org.uk>,
LKML <linux-kernel@...r.kernel.org>,
Cong Wang <xiyou.wangcong@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
"David S. Miller" <davem@...emloft.net>,
Network Development <netdev@...r.kernel.org>
Subject: Re: [PATCH] net: sched: Fix memory exposure from short TCA_U32_SEL
On Sun, Aug 26, 2018 at 10:30 AM, Jamal Hadi Salim <jhs@...atatu.com> wrote:
> We should add an nla_policy later.
What's the right way to do that for cases like this?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists