[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190120190510.GC3987@cisco>
Date: Mon, 21 Jan 2019 08:05:10 +1300
From: Tycho Andersen <tycho@...ho.ws>
To: Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Cc: linux-sparse@...r.kernel.org, kernel-hardening@...ts.openwall.com
Subject: Re: [RFC v1 0/4] static analysis of copy_to_user()
Hey Luc,
On Fri, Dec 21, 2018 at 11:47:19PM +0100, Luc Van Oostenryck wrote:
> On Thu, Dec 20, 2018 at 12:59:27PM -0700, Tycho Andersen wrote:
> > Hi all,
> >
> > A while ago I talked with various people about whether some static
> > analsys of copy_to_user() could be productive in finding infoleaks.
> > Unfortunately, due to the various issues outlined in the patch notes, it
> > doesn't seem like it is. Perhaps these checks are useful to put in just
> > to future proof ourselves against these sorts of issues, though.
> >
> > Anyway, here's the code. Thoughts welcome!
>
> Hi,
>
> I'm taking the first patch directly but I won't be able to look
> closer at the other patches until next week.
Any chance you can take a peek at these?
Cheers,
Tycho
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
