From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: helpdesk@kernel.org
Cc: bpf <bpf@vger.kernel.org>,
linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: Requests to git.kernel.org return 502
Date: Mon, 3 Nov 2025 15:57:30 -0800 [thread overview]
Message-ID: <2ab28c85-fc15-438b-aa5c-cfeb2c6917d5@linux.dev> (raw)
In-Reply-To: <d0ca5bfb-5ead-4f67-8716-d44485a8d8f7@linux.dev>
On 10/14/25 2:36 PM, Ihor Solodrai wrote:
> Hi,
>
> Today we started seeing frequent 502 errors on attempts to fetch from
> git.kernel.org in BPF CI jobs, which causes many of them to fail.
>
> Kernel Patches Daemon instance is also down because of this.
>
> Example [1]:
>
> + git remote add origin https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
> Initialized empty Git repository in /tmp/work/vmtest/vmtest/.kernel/.git/
> + git fetch --depth=64 origin master
> fatal: unable to access 'https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/': The requested URL returned error: 502
> Error: Process completed with exit code 128.
>
> https://github.com/kernel-patches/vmtest/actions/runs/18510075579/job/52750495992?pr=404
>
> Any recent changes on kernel.org side? Is this a known issue?
>
> Please let me know. Thanks.
Hi all,
HTTP 502 from git.kernel.org picked up again today.
Examples:
* https://github.com/kernel-patches/bpf/actions/runs/19052891379/job/54416890870
* https://github.com/kernel-patches/bpf/actions/runs/19052904470/job/54416948499
prev parent reply other threads:[~2025-11-03 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 21:36 Requests to git.kernel.org return 502 Ihor Solodrai
2025-11-03 23:57 ` Ihor Solodrai [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=2ab28c85-fc15-438b-aa5c-cfeb2c6917d5@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=helpdesk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
/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