From: Uladzislau Rezki <urezki@gmail.com>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
mchehab@kernel.org,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] WARNING in __vmalloc_node_range
Date: Fri, 7 May 2021 14:42:14 +0200 [thread overview]
Message-ID: <CA+KHdyWuf8iDvrmGfapVy3pRie4FOwdasbtRij39MmXr0Wpzuw@mail.gmail.com> (raw)
In-Reply-To: <20210507152954.5773592a@gmail.com>
Hello, Pavel.
Also in the commit message i see a type.
<snip>
syzbot reported WARNING in vmalloc. The problem
was in sizo size passed to vmalloc.
<snip>
Should it be "...zero size passed to vmalloc"?
--
Vlad Rezki
On Fri, May 7, 2021 at 2:29 PM Pavel Skripkin <paskripkin@gmail.com> wrote:
>
> On Fri, 7 May 2021 11:04:36 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > On Thu, May 06, 2021 at 06:00:53PM +0300, Pavel Skripkin wrote:
> > >
> > > Hi!
> > >
> > > I've already sent the patch:
> > > https://patchwork.linuxtv.org/project/linux-media/patch/20210506121211.8556-1-paskripkin@gmail.com/
> > >
> >
> > Please, always add a Fixes tag.
> >
> > Fixes: 4d43e13f723e ("V4L/DVB (4643): Multi-input patch for DVB-USB
> > device")
> >
> > regards,
> > dan carpenter
> >
>
> oh..., that's one thing I always forget about. Thanks for pointing it
> out, I'll send v2 soon
>
>
> With regards,
> Pavel Skripkin
--
Uladzislau Rezki
next prev parent reply other threads:[~2021-05-07 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 10:33 [syzbot] WARNING in __vmalloc_node_range syzbot
2021-05-06 14:22 ` Uladzislau Rezki
2021-05-06 14:57 ` Dan Carpenter
2021-05-06 15:00 ` Dmitry Vyukov
2021-05-06 15:06 ` Dan Carpenter
2021-05-06 15:00 ` Pavel Skripkin
2021-05-07 8:04 ` Dan Carpenter
2021-05-07 12:29 ` Pavel Skripkin
2021-05-07 12:42 ` Uladzislau Rezki [this message]
2021-05-07 12:45 ` Pavel Skripkin
2021-05-08 12:46 ` Dan Carpenter
2021-05-11 7:07 ` Dan Carpenter
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=CA+KHdyWuf8iDvrmGfapVy3pRie4FOwdasbtRij39MmXr0Wpzuw@mail.gmail.com \
--to=urezki@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paskripkin@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.