The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hughd@google.com,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	syzkaller-bugs@googlegroups.com, ziy@nvidia.com
Subject: Re: [syzbot] [mm?] general protection fault in shmem_mapping
Date: Fri, 14 Feb 2025 15:45:02 -0800	[thread overview]
Message-ID: <67afd57e.050a0220.21dd3.005a.GAE@google.com> (raw)
In-Reply-To: <25D9A5BF-7108-455C-8A2E-B04A3A4DF5F2@nvidia.com>

Hello,

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

failed to checkout kernel repo git@github.com:x-y-z/linux-1gb-thp.git/syzkaller_fix_20250114: failed to run ["git" "fetch" "--force" "21c4e043f63ee530c32221be8efae42773de1c65" "syzkaller_fix_20250114"]: exit status 128
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.



Tested on:

commit:         [unknown 
git tree:       git@github.com:x-y-z/linux-1gb-thp.git syzkaller_fix_20250114
kernel config:  https://syzkaller.appspot.com/x/.config?x=2cd616b6e736ca7
dashboard link: https://syzkaller.appspot.com/bug?extid=012c6245eaea0e23f7f9
compiler:       

Note: no patches were applied.

  reply	other threads:[~2025-02-14 23:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 15:48 [syzbot] [mm?] general protection fault in shmem_mapping syzbot
2025-02-14 18:57 ` Zi Yan
2025-02-14 23:26 ` Zi Yan
2025-02-14 23:26   ` syzbot
2025-02-14 23:28     ` Zi Yan
2025-02-14 23:45       ` syzbot [this message]
2025-02-15  0:13 ` [syzbot] " syzbot
2025-02-15  0:48 ` Zi Yan
2025-02-15  1:15   ` syzbot
     [not found] <2B47C642-0140-4981-BE7F-1E02676166B8@nvidia.com>
2025-02-15  0:42 ` 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=67afd57e.050a0220.21dd3.005a.GAE@google.com \
    --to=syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=ziy@nvidia.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