All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d3fe2dc5ffe9380b714b@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, muchun.song@linux.dev,
	netdev@vger.kernel.org,  osalvador@suse.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] kernel BUG in __vma_reservation_common
Date: Tue, 28 May 2024 10:24:03 -0700	[thread overview]
Message-ID: <00000000000076009c061986e67f@google.com> (raw)
In-Reply-To: <ZlYIoPEq7avOkjCW@localhost.localdomain>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+d3fe2dc5ffe9380b714b@syzkaller.appspotmail.com

Tested on:

commit:         c80d58cd mm/hugetlb: Do not call vma_add_reservation u..
git tree:       https://github.com/leberus/linux.git hugetlb-vma_resv-enomem
console output: https://syzkaller.appspot.com/x/log.txt?x=1763ba0c980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b9016f104992d69c
dashboard link: https://syzkaller.appspot.com/bug?extid=d3fe2dc5ffe9380b714b
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.


      reply	other threads:[~2024-05-28 17:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  9:18 [syzbot] [mm?] kernel BUG in __vma_reservation_common syzbot
2024-05-27 12:50 ` syzbot
2024-05-28  8:54   ` Oscar Salvador
2024-05-28  9:51   ` Oscar Salvador
2024-05-28 10:31     ` syzbot
2024-05-28  9:52   ` Oscar Salvador
2024-05-28 11:29   ` Oscar Salvador
2024-05-28 15:43     ` syzbot
2024-05-28 16:40       ` Oscar Salvador
2024-05-28 12:08   ` Oscar Salvador
2024-05-28 15:36     ` syzbot
2024-05-28 16:38   ` Oscar Salvador
2024-05-28 17:24     ` syzbot [this message]

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=00000000000076009c061986e67f@google.com \
    --to=syzbot+d3fe2dc5ffe9380b714b@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=osalvador@suse.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.