On Tue, Sep 20, 2016 at 3:28 PM, Rasmus Villemoes
wrote:
> format_decode and vsnprintf occasionally show up in perf top, so I
> went looking for places that might not need the full printf
> power. With the help of kprobes, I gathered some statistics on which
> format strings we mostly pass to vsnp
On Thu, 06 Oct 2016 00:48:59 +0200 Rasmus Villemoes
wrote:
> On Wed, Sep 21 2016, Kees Cook wrote:
>
> > On Tue, Sep 20, 2016 at 3:28 PM, Rasmus Villemoes
> > wrote:
> >
> > Heheh. Nice. :)
> >
> > Acked-by: Kees Cook
> >
>
> Andrew, ping?
Yup, I have this queued for processing after -rc1.
On Wed, Sep 21 2016, Kees Cook wrote:
> On Tue, Sep 20, 2016 at 3:28 PM, Rasmus Villemoes
> wrote:
>
> Heheh. Nice. :)
>
> Acked-by: Kees Cook
>
Andrew, ping?
On Wed, Sep 21 2016, Kees Cook wrote:
> On Tue, Sep 20, 2016 at 3:28 PM, Rasmus Villemoes
> wrote:
>> format_decode and vsnprintf occasionally show up in perf top, so I
>> went looking for places that might not need the full printf
>> power. With the help of kprobes, I gathered some statistics o
On Tue, Sep 20, 2016 at 3:28 PM, Rasmus Villemoes
wrote:
> format_decode and vsnprintf occasionally show up in perf top, so I
> went looking for places that might not need the full printf
> power. With the help of kprobes, I gathered some statistics on which
> format strings we mostly pass to vsnp
format_decode and vsnprintf occasionally show up in perf top, so I
went looking for places that might not need the full printf
power. With the help of kprobes, I gathered some statistics on which
format strings we mostly pass to vsnprintf. On a trivial desktop
workload, I hit "%x" 25% of the time,
6 matches
Mail list logo