On Sun, Jan 10, 2021 at 10:34 PM syzbot
wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 537cf4e3cc2f6cc9088dcd6162de573f603adc29
> Author: Magnus Karlsson
> Date: Fri Nov 20 11:53:39 2020 +
>
> xsk: Fix umem cleanup bug at socket destruct
>
> bisection log: https:
syzbot suspects this issue was fixed by commit:
commit 537cf4e3cc2f6cc9088dcd6162de573f603adc29
Author: Magnus Karlsson
Date: Fri Nov 20 11:53:39 2020 +
xsk: Fix umem cleanup bug at socket destruct
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=139f3dfb50
start commi
Stephen Rothwell writes:
>> All a bit mysterious. I think it's best that we revert this from
>> linux-next until we hear from Ingo. I queued a patch - I expect
>> Stephen will see and grab it, thanks.
>
> In the end I actually did the revert (of the revert) in the merge of
> the tip tree (so tha
Hi Andrew,
On Thu, 23 Jul 2020 19:50:29 -0700 Andrew Morton
wrote:
>
> On Wed, 22 Jul 2020 16:46:50 +0200 Uladzislau Rezki wrote:
>
> All a bit mysterious. I think it's best that we revert this from
> linux-next until we hear from Ingo. I queued a patch - I expect
> Stephen will see and grab
Hi Andrew,
On Thu, 23 Jul 2020 19:50:29 -0700 Andrew Morton
wrote:
>
> All a bit mysterious. I think it's best that we revert this from
> linux-next until we hear from Ingo. I queued a patch - I expect
> Stephen will see and grab it, thanks.
Wiil do.
--
Cheers,
Stephen Rothwell
pgpLGs7XQb
On Wed, 22 Jul 2020 16:46:50 +0200 Uladzislau Rezki wrote:
> > > I can check further, but it can be it was not correctly reverted,
> > > because everything should work just fine even with the revert,
> > > though i i do not understand a reason of reverting.
> >
> > Vlad, how sure are you about t
> > > syzbot has found a reproducer for the following issue on:
> > >
> > > HEAD commit:ab8be66e Add linux-next specific files for 20200720
> > > git tree: linux-next
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=161a0cc890
> > > kernel config: https://syzkaller.ap
On Mon, Jul 20, 2020 at 10:06:18PM +0200, Uladzislau Rezki wrote:
> On Mon, Jul 20, 2020 at 09:48:21AM -0700, syzbot wrote:
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit:ab8be66e Add linux-next specific files for 20200720
> > git tree: linux-next
> > c
syzbot has bisected this issue to:
commit bdbfb1d52d5e576c1d275fd8ab59b677011229e8
Author: Ingo Molnar
Date: Sun Jun 7 19:12:51 2020 +
Revert "mm/vmalloc: modify struct vmap_area to reduce its size"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166e6b7f10
start comm
On Mon, Jul 20, 2020 at 09:48:21AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit:ab8be66e Add linux-next specific files for 20200720
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=161a0cc890
> kern
syzbot has found a reproducer for the following issue on:
HEAD commit:ab8be66e Add linux-next specific files for 20200720
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=161a0cc890
kernel config: https://syzkaller.appspot.com/x/.config?x=c4bf77d63d0cf8
Hello,
syzbot found the following crash on:
HEAD commit:7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=129af75510
kernel config: https://syzkaller.appspot.com/x/.config?x=183dd243398ba7ec
das
On Tue, Dec 19, 2017 at 11:52 AM, syzbot
wrote:
> Hello,
>
> syzkaller hit the following crash on
> 6084b576dca2e898f5c101baef151f7bfdbb606d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is
13 matches
Mail list logo