From: syzbot <syzbot+18df508cf00a0598d9a6@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wojciech.gladysz@infogain.com
Subject: Re: [syzbot] [ext4?] general protection fault in __block_commit_write
Date: Mon, 01 Jul 2024 01:54:01 -0700 [thread overview]
Message-ID: <000000000000176977061c2bbdeb@google.com> (raw)
In-Reply-To: <20240701082944.17441-1-wojciech.gladysz@infogain.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo https://linux.googlesource.com/linux/kernel/git/torvalds/linux/---: failed to run ["git" "fetch" "--force" "5efaa37364b8874e2c0b1d9108beeed3d23b6a7c" "---"]: exit status 129
error: unknown option `-'
usage: git fetch [<options>] [<repository> [<refspec>...]]
or: git fetch [<options>] <group>
or: git fetch --multiple [<options>] [(<repository> | <group>)...]
or: git fetch --all [<options>]
-v, --verbose be more verbose
-q, --quiet be more quiet
--all fetch from all remotes
--set-upstream set upstream for git pull/fetch
-a, --append append to .git/FETCH_HEAD instead of overwriting
--atomic use atomic transaction to update references
--upload-pack <path> path to upload pack on remote end
-f, --force force overwrite of local reference
-m, --multiple fetch from multiple remotes
-t, --tags fetch all tags and associated objects
-n do not fetch all tags (--no-tags)
-j, --jobs <n> number of submodules fetched in parallel
--prefetch modify the refspec to place all refs within refs/prefetch/
-p, --prune prune remote-tracking branches no longer on remote
-P, --prune-tags prune local tags no longer on remote and clobber changed tags
--recurse-submodules[=<on-demand>]
control recursive fetching of submodules
--dry-run dry run
--write-fetch-head write fetched references to the FETCH_HEAD file
-k, --keep keep downloaded pack
-u, --update-head-ok allow updating of HEAD ref
--progress force progress reporting
--depth <depth> deepen history of shallow clone
--shallow-since <time>
deepen history of shallow repository based on time
--shallow-exclude <revision>
deepen history of shallow clone, excluding rev
--deepen <n> deepen history of shallow clone
--unshallow convert to a complete repository
--refetch re-fetch without negotiating common commits
--update-shallow accept refs that update .git/shallow
--refmap <refmap> specify fetch refmap
-o, --server-option <server-specific>
option to transmit
-4, --ipv4 use IPv4 addresses only
-6, --ipv6 use IPv6 addresses only
--negotiation-tip <revision>
report that we have only objects reachable from this object
--negotiate-only do not fetch a packfile; instead, print ancestors of negotiation tips
--filter <args> object filtering
--auto-maintenance run 'maintenance --auto' after fetching
--auto-gc run 'maintenance --auto' after fetching
--show-forced-updates
check for forced-updates on all updated branches
--write-commit-graph write the commit-graph after fetching
--stdin accept refspecs from stdin
Tested on:
commit: [unknown
git tree: https://linux.googlesource.com/linux/kernel/git/torvalds/linux ---
kernel config: https://syzkaller.appspot.com/x/.config?x=95dc1de8407c7270
dashboard link: https://syzkaller.appspot.com/bug?extid=18df508cf00a0598d9a6
compiler:
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=14a45512980000
next parent reply other threads:[~2024-07-01 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701082944.17441-1-wojciech.gladysz@infogain.com>
2024-07-01 8:54 ` syzbot [this message]
[not found] <20240701084542.24151-1-wojciech.gladysz@infogain.com>
2024-07-01 11:46 ` [syzbot] [ext4?] general protection fault in __block_commit_write syzbot
[not found] <20240701084553.24215-1-wojciech.gladysz@infogain.com>
2024-07-01 11:32 ` syzbot
[not found] <20240701083435.19182-1-wojciech.gladysz@infogain.com>
2024-07-01 11:18 ` syzbot
2024-02-05 9:01 syzbot
2024-05-20 1:52 ` 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=000000000000176977061c2bbdeb@google.com \
--to=syzbot+18df508cf00a0598d9a6@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wojciech.gladysz@infogain.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