Re: linux-next boot error: WARNING in kmem_cache_free

> On Jun 27, 2020, at 7:10 PM, Eric Biggers wrote: > > This bug also got reported 2 days later by the kernel test robot > (lore.kernel.org/lkml/20200623090213.GW5535@shao2-debian/). > Then it was fixed by commit 437edcaafbe3, so telling syzbot: > > #syz fix: mm, slab/slub: improve error

Re: linux-next boot error: WARNING in kmem_cache_free

[+Cc linux-mm; +Bcc linux-fsdevel] On Mon, Jun 22, 2020 at 03:28:09AM -0400, Qian Cai wrote: > > > > On Jun 22, 2020, at 2:42 AM, Dmitry Vyukov wrote: > > > > There is a reason, it's still important for us. > > But also it's not our strategy to deal with bugs by not testing > > configurations

Re: linux-next boot error: WARNING in kmem_cache_free

> On Jun 22, 2020, at 2:42 AM, Dmitry Vyukov wrote: > > There is a reason, it's still important for us. > But also it's not our strategy to deal with bugs by not testing > configurations and closing eyes on bugs, right? If it's an official > config in the kernel, it needs to be tested. If

Re: linux-next boot error: WARNING in kmem_cache_free

On Mon, Jun 22, 2020 at 8:29 AM Qian Cai wrote: > > On Jun 22, 2020, at 1:37 AM, syzbot > > wrote: > > > > WARNING: CPU: 0 PID: 0 at mm/slab.h:232 kmem_cache_free+0x0/0x200 > > mm/slab.c:2262 > > Is there any particular reason to use CONFIG_SLAB rather than CONFIG_SLUB? There is a reason,

Re: linux-next boot error: WARNING in kmem_cache_free

> On Jun 22, 2020, at 1:37 AM, syzbot > wrote: > > WARNING: CPU: 0 PID: 0 at mm/slab.h:232 kmem_cache_free+0x0/0x200 > mm/slab.c:2262 Is there any particular reason to use CONFIG_SLAB rather than CONFIG_SLUB? You are really asking for trouble to test something that almost nobody is

linux-next boot error: WARNING in kmem_cache_free

Hello, syzbot found the following crash on: HEAD commit:5a94f5bc Add linux-next specific files for 20200621 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=12a02c7610 kernel config: https://syzkaller.appspot.com/x/.config?x=e1788c418b2ddc66 dashboard

Re: WARNING in kmem_cache_free

On Sun, Apr 8, 2018 at 5:31 PM, Stephan Müller wrote: > Am Sonntag, 8. April 2018, 13:18:06 CEST schrieb Dmitry Vyukov: > > Hi Dmitry, > >> >> Running syz-repro utility on this log, I think I've found the guilty guy: >>

Re: WARNING in kmem_cache_free

On Sun, Apr 8, 2018 at 5:31 PM, Stephan Müller wrote: > Am Sonntag, 8. April 2018, 13:18:06 CEST schrieb Dmitry Vyukov: > > Hi Dmitry, > >> >> Running syz-repro utility on this log, I think I've found the guilty guy: >> https://gist.githubusercontent.com/dvyukov/1dd75d55efd238e7207af1cc38478b3a/

Re: WARNING in kmem_cache_free

Am Sonntag, 8. April 2018, 13:18:06 CEST schrieb Dmitry Vyukov: Hi Dmitry, > > Running syz-repro utility on this log, I think I've found the guilty guy: > https://gist.githubusercontent.com/dvyukov/1dd75d55efd238e7207af1cc38478b3a/ > raw/403859b56b161a6fbb158e8953fac5bb6e73b1a1/gistfile1.txt >

Re: WARNING in kmem_cache_free

Am Sonntag, 8. April 2018, 13:18:06 CEST schrieb Dmitry Vyukov: Hi Dmitry, > > Running syz-repro utility on this log, I think I've found the guilty guy: > https://gist.githubusercontent.com/dvyukov/1dd75d55efd238e7207af1cc38478b3a/ > raw/403859b56b161a6fbb158e8953fac5bb6e73b1a1/gistfile1.txt >

Re: WARNING in kmem_cache_free

On Sun, Apr 8, 2018 at 12:26 PM, Dmitry Vyukov wrote: > On Sun, Apr 8, 2018 at 8:01 AM, Matthew Wilcox wrote: >> On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: >>> On Fri, Apr 6, 2018 at 3:24 PM, syzbot >>>

Re: WARNING in kmem_cache_free

On Sun, Apr 8, 2018 at 12:26 PM, Dmitry Vyukov wrote: > On Sun, Apr 8, 2018 at 8:01 AM, Matthew Wilcox wrote: >> On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: >>> On Fri, Apr 6, 2018 at 3:24 PM, syzbot >>> wrote: >>> > Unfortunately, I don't have any reproducer for this crash

Re: WARNING in kmem_cache_free

On Sun, Apr 8, 2018 at 8:01 AM, Matthew Wilcox wrote: > On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: >> On Fri, Apr 6, 2018 at 3:24 PM, syzbot >> wrote: >> > Unfortunately, I don't have any reproducer

Re: WARNING in kmem_cache_free

On Sun, Apr 8, 2018 at 8:01 AM, Matthew Wilcox wrote: > On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: >> On Fri, Apr 6, 2018 at 3:24 PM, syzbot >> wrote: >> > Unfortunately, I don't have any reproducer for this crash yet. >> >> Interesting type of bug, I think we see this for

Re: WARNING in kmem_cache_free

On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: > On Fri, Apr 6, 2018 at 3:24 PM, syzbot > wrote: > > Unfortunately, I don't have any reproducer for this crash yet. > > Interesting type of bug, I think we see this for the

Re: WARNING in kmem_cache_free

On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: > On Fri, Apr 6, 2018 at 3:24 PM, syzbot > wrote: > > Unfortunately, I don't have any reproducer for this crash yet. > > Interesting type of bug, I think we see this for the first time. Can you focus syzbot to try to find a

Re: WARNING in kmem_cache_free

On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: > Interesting type of bug, I think we see this for the first time. > > Al, do you see how this can happen? putname() on something that hasn't come from getname(). Short of reproducer, I don't see what can be done - it can be any

Re: WARNING in kmem_cache_free

On Fri, Apr 06, 2018 at 03:33:36PM +0200, Dmitry Vyukov wrote: > Interesting type of bug, I think we see this for the first time. > > Al, do you see how this can happen? putname() on something that hasn't come from getname(). Short of reproducer, I don't see what can be done - it can be any

Re: WARNING in kmem_cache_free

On Fri, Apr 6, 2018 at 3:24 PM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > f2d285669aae656dfeafa0bf25e86bbbc5d22329 (Tue Apr 3 17:45:39 2018 +) > Merge tag 'pm-4.17-rc1' of >

Re: WARNING in kmem_cache_free

On Fri, Apr 6, 2018 at 3:24 PM, syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > f2d285669aae656dfeafa0bf25e86bbbc5d22329 (Tue Apr 3 17:45:39 2018 +) > Merge tag 'pm-4.17-rc1' of > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm > syzbot dashboard

WARNING in kmem_cache_free

Hello, syzbot hit the following crash on upstream commit f2d285669aae656dfeafa0bf25e86bbbc5d22329 (Tue Apr 3 17:45:39 2018 +) Merge tag 'pm-4.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm syzbot dashboard link:

WARNING in kmem_cache_free

Hello, syzbot hit the following crash on upstream commit f2d285669aae656dfeafa0bf25e86bbbc5d22329 (Tue Apr 3 17:45:39 2018 +) Merge tag 'pm-4.17-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm syzbot dashboard link: