[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+yMNRQHRj8haLfNCst1C_7TDPf8axyUBatVWEvWbVmmQ@mail.gmail.com>
Date: Fri, 13 Jan 2017 15:15:55 -0800
From: Kees Cook <keescook@...omium.org>
To: PaX Team <pageexec@...email.hu>
Cc: "AKASHI, Takahiro" <takahiro.akashi@...aro.org>, Mark Rutland <mark.rutland@....com>,
park jinbum <jinb.park7@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>
Subject: Re: Introduction
On Fri, Jan 13, 2017 at 3:09 PM, PaX Team <pageexec@...email.hu> wrote:
>> fs/read_write.c: In function ‘new_sync_write’:
>> fs/read_write.c:490:15: note: userspace variable will be forcibly initialized
>> struct iovec iov = { .iov_base = (void __user *)buf, .iov_len = len };
>
> this is a designated initializer which doesn't match the object constructor
> the plugin looks for.
What would an object constructor look like? When I had it report the
times it skipped forced initialization, the code mostly looked like
designated initializers. All I found in the gimple were SSAs. Nothing
jumped out at me as being an initializer.
--
Kees Cook
Nexus Security
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.
