On Tue, Nov 20, 2018 at 12:08 PM, Jeff Layton wrote:
> On Tue, 2018-11-20 at 07:57 +0100, Dmitry Vyukov wrote:
>> On Sat, Nov 17, 2018 at 3:03 PM, Bruce Fields wrote:
>> > On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote:
>> > > Thanks for the explanation, Dmitry. I've added the tag to
On Tue, 2018-11-20 at 07:57 +0100, Dmitry Vyukov wrote:
> On Sat, Nov 17, 2018 at 3:03 PM, Bruce Fields wrote:
> > On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote:
> > > Thanks for the explanation, Dmitry. I've added the tag to the patch in
> > > my tree. It should show up in linux-nex
On Sat, Nov 17, 2018 at 3:03 PM, Bruce Fields wrote:
> On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote:
>> Thanks for the explanation, Dmitry. I've added the tag to the patch in
>> my tree. It should show up in linux-next soon.
>>
>> I still find it a little misleading to say that syzb
On Sat, Nov 17, 2018 at 08:33:27AM -0500, Jeff Layton wrote:
> Thanks for the explanation, Dmitry. I've added the tag to the patch in
> my tree. It should show up in linux-next soon.
>
> I still find it a little misleading to say that syzbot reported a bug
> when it actually found a bug inside an
On Fri, 2018-11-16 at 12:37 -0800, Dmitry Vyukov wrote:
> On Thu, Nov 15, 2018 at 3:41 PM, NeilBrown wrote:
> > On Thu, Nov 15 2018, Dmitry Vyukov wrote:
> >
> > > On Wed, Nov 14, 2018 at 2:36 AM, Jeff Layton wrote:
> > > > On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote:
> > > > > On Tue, No
On Thu, Nov 15, 2018 at 3:41 PM, NeilBrown wrote:
> On Thu, Nov 15 2018, Dmitry Vyukov wrote:
>
>> On Wed, Nov 14, 2018 at 2:36 AM, Jeff Layton wrote:
>>> On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote:
On Tue, Nov 13 2018, Jeff Layton wrote:
> On Mon, 2018-11-12 at 12:34 -0800
On Thu, Nov 15 2018, Dmitry Vyukov wrote:
> On Wed, Nov 14, 2018 at 2:36 AM, Jeff Layton wrote:
>> On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote:
>>> On Tue, Nov 13 2018, Jeff Layton wrote:
>>>
>>> > On Mon, 2018-11-12 at 12:34 -0800, syzbot wrote:
>>> > > Hello,
>>> > >
>>> > > syzbot found
On Wed, Nov 14, 2018 at 2:36 AM, Jeff Layton wrote:
> On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote:
>> On Tue, Nov 13 2018, Jeff Layton wrote:
>>
>> > On Mon, 2018-11-12 at 12:34 -0800, syzbot wrote:
>> > > Hello,
>> > >
>> > > syzbot found the following crash on:
>> > >
>> > > HEAD commit:
On Wed, 2018-11-14 at 07:40 +1100, NeilBrown wrote:
> On Tue, Nov 13 2018, Jeff Layton wrote:
>
> > On Mon, 2018-11-12 at 12:34 -0800, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:442b8cea2477 Add linux-next specific files for 20181109
>
On Tue, Nov 13 2018, Jeff Layton wrote:
> On Mon, 2018-11-12 at 12:34 -0800, syzbot wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:442b8cea2477 Add linux-next specific files for 20181109
>> git tree: linux-next
>> console output: https://syzkaller.appspot
syzbot has found a reproducer for the following crash on:
HEAD commit:442b8cea2477 Add linux-next specific files for 20181109
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12fbd90540
kernel config: https://syzkaller.appspot.com/x/.config?x=2f72bdb11
On Mon, 2018-11-12 at 12:34 -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:442b8cea2477 Add linux-next specific files for 20181109
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=115dbad540
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:442b8cea2477 Add linux-next specific files for 20181109
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=115dbad540
kernel config: https://syzkaller.appspot.com/x/.config?x=2f72bdb11df9fbe8
dashb
13 matches
Mail list logo