On 2019-03-11 17:37, Dmitry Vyukov wrote:
On Mon, Mar 11, 2019 at 5:36 PM syzbot
wrote:
> On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev wrote:
>> On 2019-03-11 14:45, Dmitry Vyukov wrote:
>> > On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev wrote:
>> >>
>> >> Hi Andrew,
>> >>
>> >> I thought
On Mon, Mar 11, 2019 at 5:36 PM syzbot
wrote:
>
> > On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev wrote:
>
> >> On 2019-03-11 14:45, Dmitry Vyukov wrote:
> >> > On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev wrote:
> >> >>
> >> >> Hi Andrew,
> >> >>
> >> >> I thought "epoll: loosen irq safety in
On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev wrote:
On 2019-03-11 14:45, Dmitry Vyukov wrote:
> On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev wrote:
>>
>> Hi Andrew,
>>
>> I thought "epoll: loosen irq safety in ep_poll_callback()" patch was
>> removed from your tree, at least I got a notific
On Mon, Mar 11, 2019 at 2:53 PM Roman Penyaev wrote:
>
> On 2019-03-11 14:45, Dmitry Vyukov wrote:
> > On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev wrote:
> >>
> >> Hi Andrew,
> >>
> >> I thought "epoll: loosen irq safety in ep_poll_callback()" patch was
> >> removed from your tree, at least I g
On 2019-03-11 14:45, Dmitry Vyukov wrote:
On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev wrote:
Hi Andrew,
I thought "epoll: loosen irq safety in ep_poll_callback()" patch was
removed from your tree, at least I got a notification on 9th of
january,
also I do not see it in the linux-next tree
On Mon, Mar 11, 2019 at 2:37 PM Roman Penyaev wrote:
>
> Hi Andrew,
>
> I thought "epoll: loosen irq safety in ep_poll_callback()" patch was
> removed from your tree, at least I got a notification on 9th of january,
> also I do not see it in the linux-next tree.
>
> Should I ignore this syzbot mes
Hi Andrew,
I thought "epoll: loosen irq safety in ep_poll_callback()" patch was
removed from your tree, at least I got a notification on 9th of january,
also I do not see it in the linux-next tree.
Should I ignore this syzbot message?
--
Roman
On 2019-03-11 14:14, syzbot wrote:
syzbot has bis
syzbot has bisected this bug to:
commit f92cacf118171208f62519d92502a8dd0341286d
Author: Roman Penyaev
Date: Tue Jan 8 01:15:44 2019 +
epoll: loosen irq safety in ep_poll_callback()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=107ae15f20
start commit: f92cacf1 e
On 2019-01-08 07:00, Dmitry Vyukov wrote:
On Tue, Jan 8, 2019 at 6:59 AM syzbot
wrote:
Hello,
syzbot found the following crash on:
HEAD commit:139287cc2cc0 Add linux-next specific files for
20190108
git tree: linux-next
console output:
https://syzkaller.appspot.com/x/log.txt?x=1
syzbot has found a reproducer for the following crash on:
HEAD commit:139287cc2cc0 Add linux-next specific files for 20190108
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14c9dd4b40
kernel config: https://syzkaller.appspot.com/x/.config?x=1521b074f
On Tue, Jan 8, 2019 at 6:59 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:139287cc2cc0 Add linux-next specific files for 20190108
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=16f563d740
> kernel config: htt
Hello,
syzbot found the following crash on:
HEAD commit:139287cc2cc0 Add linux-next specific files for 20190108
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16f563d740
kernel config: https://syzkaller.appspot.com/x/.config?x=1521b074ff5a5bdf
dashb
12 matches
Mail list logo