I got one more report of a similar bug:
AddressSanitizer: heap-buffer-overflow on address 8800205f0e40
Write of size 1 by thread T14005:
[] ftrace_event_write+0xe2/0x130
./kernel/trace/trace_events.c:583
[] vfs_write+0x127/0x2f0 ??:0
[] SyS_write+0x72/0xd0 ??:0
[] system_call_fastpath+0x16
On Wed, Oct 02, 2013 at 04:18:02PM -0400, Steven Rostedt wrote:
> On Wed, 2013-10-02 at 14:57 -0400, Dave Jones wrote:
>
> > And that's the cause. I wonder what was being opened.
> > Do you happen to have a trinity-child log for that thread ?
>
> Thanks for the update. This definitely looks
On Wed, 2013-10-02 at 14:57 -0400, Dave Jones wrote:
> And that's the cause. I wonder what was being opened.
> Do you happen to have a trinity-child log for that thread ?
Thanks for the update. This definitely looks like the bug, and explains
a lot. I'll look into this, as I'm currently at a conf
On Wed, Oct 2, 2013 at 10:57 PM, Dave Jones wrote:
> And that's the cause. I wonder what was being opened.
> Do you happen to have a trinity-child log for that thread ?
Unfortunately not.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
On Wed, Oct 02, 2013 at 10:38:01PM +0400, Andrey Konovalov wrote:
> Hi!
>
> I am working on AddressSanitizer -- a tool that detects use-after-free
> and out-of-bounds bugs
> (https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel).
> Below is one of the bug reports that I
5 matches
Mail list logo