linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, fmdefrancesco@gmail.com,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] memory leak in __get_metapage
Date: Thu, 06 Oct 2022 02:43:22 -0700	[thread overview]
Message-ID: <000000000000280f3e05ea5a868a@google.com> (raw)
In-Reply-To: <2217443.iZASKD2KPV@mypc>

Hello,

syzbot tried to test the proposed patch but the build/boot failed:

failed to checkout kernel repo git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/6.0: failed to run ["git" "fetch" "--force" "f569e972c8e9057ee9c286220c83a480ebf30cc5" "6.0"]: exit status 128
fatal: couldn't find remote ref 6.0



Tested on:

commit:         [unknown 
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 6.0
dashboard link: https://syzkaller.appspot.com/bug?extid=389b82b29093b3e2640a
compiler:       
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1634a658880000



  reply	other threads:[~2022-10-06  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0000000000008a5a2e05ea318aa9@google.com>
2022-10-04  8:52 ` [syzbot] memory leak in __get_metapage Dmitry Vyukov
2022-10-06  1:15 ` Fabio M. De Francesco
2022-10-06  1:16   ` syzbot
2022-10-11 11:00   ` syzbot
2022-10-06  1:20 ` Fabio M. De Francesco
2022-10-06  1:20   ` syzbot
2022-10-11 10:32   ` syzbot
2022-10-06  1:23 ` Fabio M. De Francesco
2022-10-06  1:23   ` syzbot
2022-10-11 10:32   ` syzbot
2022-10-06  1:28 ` Fabio M. De Francesco
2022-10-06  9:43   ` syzbot [this message]
2022-10-06 19:43 ` Fabio M. De Francesco
2022-10-06 22:03   ` syzbot
2022-10-06 23:26 ` Fabio M. De Francesco
2022-10-06 23:54   ` 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=000000000000280f3e05ea5a868a@google.com \
    --to=syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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).