netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: syzbot <syzbot+c2f6f09fe907a838effb@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, coreteam@netfilter.org,
	davem@davemloft.net, dsahern@kernel.org, fw@strlen.de,
	kadlec@netfilter.org, kuba@kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
	pablo@netfilter.org, syzkaller-bugs@googlegroups.com,
	yoshfuji@linux-ipv6.org
Subject: Re: [syzbot] WARNING: zero-size vmalloc in corrupted
Date: Wed, 23 Jun 2021 19:28:37 +0300	[thread overview]
Message-ID: <20210623192837.13792eae@gmail.com> (raw)
In-Reply-To: <20210623191928.69d279d1@gmail.com>

On Wed, 23 Jun 2021 19:19:28 +0300
Pavel Skripkin <paskripkin@gmail.com> wrote:

> On Wed, 23 Jun 2021 02:15:23 -0700
> syzbot <syzbot+c2f6f09fe907a838effb@syzkaller.appspotmail.com> wrote:
> 
> > Hello,
> > 
> > syzbot found the following issue on:
> > 
> > HEAD commit:    13311e74 Linux 5.13-rc7
> > git tree:       upstream
> > console output:
> > https://syzkaller.appspot.com/x/log.txt?x=15d01e58300000 kernel
> > config:  https://syzkaller.appspot.com/x/.config?x=42ecca11b759d96c
> > dashboard link:
> > https://syzkaller.appspot.com/bug?extid=c2f6f09fe907a838effb syz
> > repro:
> > https://syzkaller.appspot.com/x/repro.syz?x=14bb89e8300000 C
> > reproducer:
> > https://syzkaller.appspot.com/x/repro.c?x=17cc51b8300000
> > 
> > The issue was bisected to:
> > 
> > commit f9006acc8dfe59e25aa75729728ac57a8d84fc32
> > Author: Florian Westphal <fw@strlen.de>
> > Date:   Wed Apr 21 07:51:08 2021 +0000
> > 
> >     netfilter: arp_tables: pass table pointer via nf_hook_ops
> > 
> > bisection log:
> > https://syzkaller.appspot.com/x/bisect.txt?x=13b88400300000 final
> > oops:
> > https://syzkaller.appspot.com/x/report.txt?x=10788400300000 console
> > output: https://syzkaller.appspot.com/x/log.txt?x=17b88400300000
> > 
> 
> This one is similar to previous zero-size vmalloc, I guess :)
> 
> #syz test
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> 
> 

Hah, I didn't notice that this one is already fixed by me. But the
patch is in the media tree, it's not upstreamed yet:  

https://git.linuxtv.org/media_tree.git/commit/?id=c680ed46e418e9c785d76cf44eb33bfd1e8cf3f6

So, 

#syz dup: WARNING: zero-size vmalloc in dvb_dmx_init

With regards,
Pavel Skripkin

  reply	other threads:[~2021-06-23 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  9:15 [syzbot] WARNING: zero-size vmalloc in corrupted syzbot
2021-06-23 16:19 ` Pavel Skripkin
2021-06-23 16:28   ` Pavel Skripkin [this message]
2021-06-23 16:28     ` syzbot
2021-06-23 16:28     ` syzbot
2021-06-24  6:17       ` Dmitry Vyukov
2021-06-23 16:37   ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210623192837.13792eae@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=fw@strlen.de \
    --cc=kadlec@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=syzbot+c2f6f09fe907a838effb@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).