linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Skripkin <paskripkin@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+c87d2efb740931ec76c7@syzkaller.appspotmail.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	pbonzini@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in kvm_dev_ioctl
Date: Mon, 5 Jul 2021 14:36:52 +0300	[thread overview]
Message-ID: <20210705143652.56b3d68b@gmail.com> (raw)
In-Reply-To: <CACT4Y+Yk5v3=2V_t77RSqACNYQb6PmDM0Mst6N1QEgz9CdYrqw@mail.gmail.com>

On Mon, 5 Jul 2021 07:54:59 +0200
Dmitry Vyukov <dvyukov@google.com> wrote:

> On Sat, Jul 3, 2021 at 9:12 AM Pavel Skripkin <paskripkin@gmail.com>
> wrote:
> >
> > On Fri, 02 Jul 2021 23:05:26 -0700
> > syzbot <syzbot+c87d2efb740931ec76c7@syzkaller.appspotmail.com>
> > wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    e058a84b Merge tag 'drm-next-2021-07-01' of
> > > git://anongit... git tree:       upstream
> > > console output:
> > > https://syzkaller.appspot.com/x/log.txt?x=171fbbdc300000 kernel
> > > config:
> > > https://syzkaller.appspot.com/x/.config?x=8c46abb9076f44dc
> > > dashboard link:
> > > https://syzkaller.appspot.com/bug?extid=c87d2efb740931ec76c7 syz
> > > repro: https://syzkaller.appspot.com/x/repro.syz?x=119d1efc300000
> > > C reproducer:
> > > https://syzkaller.appspot.com/x/repro.c?x=16c58c28300000
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to
> > > the commit: Reported-by:
> > > syzbot+c87d2efb740931ec76c7@syzkaller.appspotmail.com
> > >
> >
> > Corresponding fix was sent about 2 days ago
> > https://patchwork.kernel.org/project/kvm/patch/20210701195500.27097-1-paskripkin@gmail.com/
> 
> Hi Pavel,
> 
> Thanks for checking. Let's tell syzbot about the fix:
> 
> #syz fix: kvm: debugfs: fix memory leak in kvm_create_vm_debugfs


Hi, Dmitry!

Sorry for stupid question :)

I don't see, that my patch was applied, so syzbot will save the patch
name and will test it after it will be applied? I thought about
sending `syz fix` command, but I was sure that syzbot takes only
accepted patches.



With regards,
Pavel Skripkin

  reply	other threads:[~2021-07-05 11:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  6:05 [syzbot] memory leak in kvm_dev_ioctl syzbot
2021-07-03  7:12 ` Pavel Skripkin
2021-07-05  5:54   ` Dmitry Vyukov
2021-07-05 11:36     ` Pavel Skripkin [this message]
2021-07-05 11:47       ` Dmitry Vyukov
2021-07-05 13:31         ` Pavel Skripkin

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=20210705143652.56b3d68b@gmail.com \
    --to=paskripkin@gmail.com \
    --cc=dvyukov@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=syzbot+c87d2efb740931ec76c7@syzkaller.appspotmail.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 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).