From: "Stephan Müller" <smueller@chronox.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+9c251bdd09f83b92ba95@syzkaller.appspotmail.com>,
davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KMSAN: uninit-value in af_alg_free_areq_sgls
Date: Thu, 05 Jul 2018 20:45:23 +0200 [thread overview]
Message-ID: <1626520.Rx0128ICKU@positron.chronox.de> (raw)
In-Reply-To: <000000000000846e9e0570438176@google.com>
Am Donnerstag, 5. Juli 2018, 19:02:01 CEST schrieb syzbot:
Hi Dimitry,
does the syzkaller somehow uses the "---" separator as part of the URL?
Thanks
> Hello,
>
> syzbot tried to test the proposed patch but build/boot failed:
>
> failed to checkout kernel repo https://github.com/google/kmsan.git/---:
> failed to run /usr/bin/git [git fetch https://github.com/google/kmsan.git
> ---]: 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
> -a, --append append to .git/FETCH_HEAD instead of overwriting
> --upload-pack <path> path to upload pack on remote end
> -f, --force force overwrite of local branch
> -m, --multiple fetch from multiple remotes
> -t, --tags fetch all tags and associated objects
> -n do not fetch all tags (--no-tags)
> -p, --prune prune remote-tracking branches no longer on
> remote --recurse-submodules[=<on-demand>]
> control recursive fetching of submodules
> --dry-run dry run
> -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
> --unshallow convert to a complete repository
> --update-shallow accept refs that update .git/shallow
> --refmap <refmap> specify fetch refmap
>
>
>
>
> Tested on:
>
> commit: [unknown]
> git tree: https://github.com/google/kmsan.git/---> compiler: clang version 7.0.0 (trunk 334104)
> patch: https://syzkaller.appspot.com/x/patch.diff?x=1207511c400000
Ciao
Stephan
next prev parent reply other threads:[~2018-07-05 18:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:07 KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-04-08 17:57 ` [PATCH] AF_ALG: register completely initialized request in list Stephan Müller
2018-04-09 7:51 ` Dmitry Vyukov
2018-04-09 7:54 ` Stephan Mueller
2018-07-04 23:37 ` Eric Biggers
2018-07-05 7:49 ` Stephan Müller
2018-07-05 8:43 ` Dmitry Vyukov
2018-07-05 15:58 ` [PATCH v2] AF_ALG: Initialize sg_num_bytes in error code path Stephan Müller
2018-07-05 17:02 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-05 18:45 ` Stephan Müller [this message]
2018-07-06 7:38 ` Dmitry Vyukov
2018-07-06 7:41 ` Stephan Mueller
2018-07-06 7:44 ` Dmitry Vyukov
2018-07-06 7:50 ` [PATCH v3] AF_ALG: Initialize sg_num_bytes in error code path Stephan Müller
2018-07-06 7:58 ` Dmitry Vyukov
2018-07-06 8:09 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-06 8:19 ` Dmitry Vyukov
2018-07-06 15:30 ` Dmitry Vyukov
2018-07-06 15:55 ` syzbot
2018-07-06 16:27 ` Stephan Mueller
2018-07-06 21:57 ` [PATCH v3] AF_ALG: Initialize sg_num_bytes in error code path Eric Biggers
2018-07-07 18:41 ` [PATCH v4] " Stephan Müller
2018-07-07 19:01 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-13 10:34 ` [PATCH v4] AF_ALG: Initialize sg_num_bytes in error code path Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2018-07-20 12:14 [PATCH 4.14 56/92] crypto: af_alg - " Greg Kroah-Hartman
2018-07-20 12:54 ` KMSAN: uninit-value in af_alg_free_areq_sgls syzbot
2018-07-20 12:14 [PATCH 4.17 066/101] crypto: af_alg - Initialize sg_num_bytes in error code path Greg Kroah-Hartman
2018-07-20 13:08 ` KMSAN: uninit-value in af_alg_free_areq_sgls 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=1626520.Rx0128ICKU@positron.chronox.de \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9c251bdd09f83b92ba95@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox