On Mon, Mar 13, 2017 at 11:15:29AM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
> wrote:
> > On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
> >> On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
> >> wrote:
> >> > On Thu, Feb 02, 2017 at 06:48:
On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
wrote:
> On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
>> On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
>> wrote:
>> > On Thu, Feb 02, 2017 at 06:48:48PM +0100, Dmitry Vyukov wrote:
>> >> Hello,
>> >>
>> >> Syzkaller fuzzer
On Fri, Mar 3, 2017 at 8:36 AM, Dmitry Vyukov wrote:
> On Thu, Mar 2, 2017 at 8:37 PM, Greg Kroah-Hartman
> wrote:
>>> >> This is hurting us badly.
>>> >
>>> > Really? How? Are you hitting this a lot? Why now and never before?
>>> > Are you really out of memory?
>>>
>>>
>>> This crashes our te
On Thu, Mar 2, 2017 at 8:37 PM, Greg Kroah-Hartman
wrote:
>> >> This is hurting us badly.
>> >
>> > Really? How? Are you hitting this a lot? Why now and never before?
>> > Are you really out of memory?
>>
>>
>> This crashes our test bots a lot.
>> Why now... I don't have exact answer. Probably
On Thu, Mar 02, 2017 at 08:30:48PM +0100, Dmitry Vyukov wrote:
> On Thu, Mar 2, 2017 at 8:27 PM, Greg Kroah-Hartman
> wrote:
> >> > >> >> Hello,
> >> > >> >>
> >> > >> >> Syzkaller fuzzer started crashing kernel with the following
> >> > >> >> panics:
> >> > >> >>
> >> > >
On Tue, Feb 28, 2017 at 7:11 PM, Dmitry Vyukov wrote:
> On Fri, Feb 17, 2017 at 10:51 PM, Dmitry Vyukov wrote:
> >> >> Hello,
> >> >>
> >> >> Syzkaller fuzzer started crashing kernel with the following panics:
> >> >>
> >> >> Kernel panic - not syncing: Couldn't open N_TTY ldi
On Thu, Mar 02, 2017 at 07:27:35PM +0100, Dmitry Vyukov wrote:
> On Tue, Feb 28, 2017 at 7:11 PM, Dmitry Vyukov wrote:
> > On Fri, Feb 17, 2017 at 10:51 PM, Dmitry Vyukov wrote:
> > >> >> Hello,
> > >> >>
> > >> >> Syzkaller fuzzer started crashing kernel with the following
> > >
On Thu, Mar 2, 2017 at 8:27 PM, Greg Kroah-Hartman
wrote:
>> > >> >> Hello,
>> > >> >>
>> > >> >> Syzkaller fuzzer started crashing kernel with the following
>> > >> >> panics:
>> > >> >>
>> > >> >> Kernel panic - not syncing: Couldn't open N_TTY ldisc for
>> > >> >>
On Fri, Feb 17, 2017 at 10:51 PM, Dmitry Vyukov wrote:
>> >> Hello,
>> >>
>> >> Syzkaller fuzzer started crashing kernel with the following panics:
>> >>
>> >> Kernel panic - not syncing: Couldn't open N_TTY ldisc for ircomm0
>> >> --- error -12.
>> >> CPU: 0 PI
On Tue, Feb 7, 2017 at 11:51 AM, Dmitry Vyukov wrote:
> On Tue, Feb 7, 2017 at 11:43 AM, Greg Kroah-Hartman
> wrote:
>> On Tue, Feb 07, 2017 at 11:24:13AM +0100, Dmitry Vyukov wrote:
>>> On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
>>> wrote:
>>> > On Thu, Feb 02, 2017 at 07:03:41PM +0100,
On Tue, Feb 7, 2017 at 11:43 AM, Greg Kroah-Hartman
wrote:
> On Tue, Feb 07, 2017 at 11:24:13AM +0100, Dmitry Vyukov wrote:
>> On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
>> wrote:
>> > On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
>> >> On Thu, Feb 2, 2017 at 6:55 PM, Gre
On Tue, Feb 07, 2017 at 11:24:13AM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
> wrote:
> > On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
> >> On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
> >> wrote:
> >> > On Thu, Feb 02, 2017 at 06:48:
On Thu, Feb 2, 2017 at 7:23 PM, Greg Kroah-Hartman
wrote:
> On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
>> On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
>> wrote:
>> > On Thu, Feb 02, 2017 at 06:48:48PM +0100, Dmitry Vyukov wrote:
>> >> Hello,
>> >>
>> >> Syzkaller fuzzer
On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
> wrote:
> > On Thu, Feb 02, 2017 at 06:48:48PM +0100, Dmitry Vyukov wrote:
> >> Hello,
> >>
> >> Syzkaller fuzzer started crashing kernel with the following panics:
> >>
> >> Kernel
On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
wrote:
> On Thu, Feb 02, 2017 at 06:48:48PM +0100, Dmitry Vyukov wrote:
>> Hello,
>>
>> Syzkaller fuzzer started crashing kernel with the following panics:
>>
>> Kernel panic - not syncing: Couldn't open N_TTY ldisc for ircomm0 --- error
>> -12.
On Thu, Feb 02, 2017 at 06:48:48PM +0100, Dmitry Vyukov wrote:
> Hello,
>
> Syzkaller fuzzer started crashing kernel with the following panics:
>
> Kernel panic - not syncing: Couldn't open N_TTY ldisc for ircomm0 --- error
> -12.
> CPU: 0 PID: 5637 Comm: syz-executor3 Not tainted 4.9.0 #6
> Har
Hello,
Syzkaller fuzzer started crashing kernel with the following panics:
Kernel panic - not syncing: Couldn't open N_TTY ldisc for ircomm0 --- error -12.
CPU: 0 PID: 5637 Comm: syz-executor3 Not tainted 4.9.0 #6
Hardware name: Google Google Compute Engine/Google Compute Engine,
BIOS Google 01/0
17 matches
Mail list logo