All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, fmdefrancesco@gmail.com,
	ira.weiny@intel.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 15:03:21 -0700	[thread overview]
Message-ID: <000000000000947b3a05ea64dc75@google.com> (raw)
In-Reply-To: <12068295.O9o76ZdvQC@mypc>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
SYZFATAL: executor failed NUM times: executor NUM: exit status NUM

2022/10/06 22:02:25 SYZFATAL: executor failed 11 times: executor 0: exit status 67
SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)
loop exited with status 67

SYZFAIL: wrong response packet
 (errno 16: Device or resource busy)
loop exited with status 67


Tested on:

commit:         ffb39098 Merge tag 'linux-kselftest-kunit-6.1-rc1' of ..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167fffb8880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=10f41fbb818af57a
dashboard link: https://syzkaller.appspot.com/bug?extid=389b82b29093b3e2640a
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

Note: no patches were applied.


  reply	other threads:[~2022-10-06 22:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  8:49 [syzbot] memory leak in __get_metapage syzbot
2022-10-04  8:52 ` 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
2022-10-06 19:43 ` Fabio M. De Francesco
2022-10-06 22:03   ` syzbot [this message]
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=000000000000947b3a05ea64dc75@google.com \
    --to=syzbot+389b82b29093b3e2640a@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=ira.weiny@intel.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 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.