From: Salvatore Bonaccorso <carnil@debian.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Florian Lehner <dev@der-flo.net>,
Linus Torvalds <torvalds@linuxfoundation.org>,
X86 ML <x86@kernel.org>, "David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Hsin-Wei Hung <hsinweih@uci.edu>,
Steven Rostedt <rostedt@goodmis.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Maguire <alan.maguire@oracle.com>,
Rik van Riel <riel@surriel.com>, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH bpf 1/2] mm: Fix copy_from_user_nofault().
Date: Thu, 6 Apr 2023 22:17:01 +0200 [thread overview]
Message-ID: <ZC8ovRMLxL5ehzWu@eldamar.lan> (raw)
In-Reply-To: <CAADnVQKyRpg=-uxCH6eNxPfvUCS8tKSe-AV-1304rRdTYxG1JQ@mail.gmail.com>
Hi,
On Sat, Mar 25, 2023 at 12:47:17PM -0700, Alexei Starovoitov wrote:
> On Sat, Mar 25, 2023 at 7:55 AM Florian Lehner <dev@der-flo.net> wrote:
> >
> > 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>
>
> Thanks for testing and for bumping the thread.
> The fix slipped through the cracks.
>
> Looking at the stack trace in bugzilla the patch set
> should indeed fix the issue, since the kernel is deadlocking on:
> copy_from_user_nofault -> check_object_size -> find_vmap_area -> spin_lock
>
> I'm travelling this and next week, so if you can take over
> the whole patch set and roll in the tweak that was proposed back in January:
>
> - if (is_vmalloc_addr(ptr)) {
> + if (is_vmalloc_addr(ptr) && !pagefault_disabled())
>
> and respin for the bpf tree our group maintainers can review and apply
> while I'm travelling.
Anyone can pick it up as suggested by Alexei, and propose that to the
bpf tree maintainers?
Regards,
Salvatore
next prev parent reply other threads:[~2023-04-06 20:17 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
2023-03-25 19:47 ` Alexei Starovoitov
2023-04-06 20:17 ` Salvatore Bonaccorso [this message]
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=ZC8ovRMLxL5ehzWu@eldamar.lan \
--to=carnil@debian.org \
--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=dev@der-flo.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.