BPF List
 help / color / mirror / Atom feed
From: Florian Lehner <dev@der-flo.net>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: torvalds@linuxfoundation.org, x86@kernel.org,
	davem@davemloft.net, daniel@iogearbox.net, andrii@kernel.org,
	peterz@infradead.org, keescook@chromium.org, tglx@linutronix.de,
	hsinweih@uci.edu, rostedt@goodmis.org, vegard.nossum@oracle.com,
	gregkh@linuxfoundation.org, alan.maguire@oracle.com,
	dylany@meta.com, riel@surriel.com, bpf@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [PATCH bpf 1/2] mm: Fix copy_from_user_nofault().
Date: Sat, 25 Mar 2023 15:55:27 +0100	[thread overview]
Message-ID: <ZB8LX/BKPgvzfvcm@der-flo.net> (raw)
In-Reply-To: <20230118051443.78988-1-alexei.starovoitov@gmail.com>

With this patch applied on top of bpf/bpf-next (55fbae05) the system no longer runs into a total freeze as reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033398.

Tested-by: Florian Lehner <dev@der-flo.net>


  parent reply	other threads:[~2023-03-25 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  5:14 [PATCH bpf 1/2] mm: Fix copy_from_user_nofault() Alexei Starovoitov
2023-01-18  5:14 ` [PATCH bpf 2/2] perf: Fix arch_perf_out_copy_user() Alexei Starovoitov
2023-01-18 21:32 ` [PATCH bpf 1/2] mm: Fix copy_from_user_nofault() Hsin-Wei Hung
2023-01-19 16:52 ` Kees Cook
2023-01-19 19:21   ` Alexei Starovoitov
2023-01-19 20:08     ` Kees Cook
2023-01-19 20:14       ` Alexei Starovoitov
2023-01-19 20:28       ` Alexei Starovoitov
2023-03-25 14:55 ` Florian Lehner [this message]
2023-03-25 19:47   ` Alexei Starovoitov
2023-04-06 20:17     ` Salvatore Bonaccorso
2023-04-06 20:24       ` Alexei Starovoitov

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=ZB8LX/BKPgvzfvcm@der-flo.net \
    --to=dev@der-flo.net \
    --cc=alan.maguire@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dylany@meta.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsinweih@uci.edu \
    --cc=keescook@chromium.org \
    --cc=kernel-team@fb.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linuxfoundation.org \
    --cc=vegard.nossum@oracle.com \
    --cc=x86@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