Linux Kernel Mentees list
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Kurt Manucredo <fuzzybritches0@gmail.com>
Cc: nathan@kernel.org, songliubraving@fb.com, kafai@fb.com,
	syzbot+bed360704c521841c85d@syzkaller.appspotmail.com,
	hawk@kernel.org, daniel@iogearbox.net, yhs@fb.com,
	linux-kernel@vger.kernel.org, john.fastabend@gmail.com,
	andrii@kernel.org, ast@kernel.org,
	syzkaller-bugs@googlegroups.com,
	clang-built-linux@googlegroups.com, ndesaulniers@google.com,
	netdev@vger.kernel.org, kpsingh@kernel.org, kuba@kernel.org,
	bpf@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	davem@davemloft.net
Subject: Re: [PATCH v3] bpf: core: fix shift-out-of-bounds in ___bpf_prog_run
Date: Thu, 3 Jun 2021 06:43:28 +0200	[thread overview]
Message-ID: <YLhd8BL3HGItbXmx@kroah.com> (raw)
In-Reply-To: <20210602212726.7-1-fuzzybritches0@gmail.com>

On Wed, Jun 02, 2021 at 09:27:26PM +0000, Kurt Manucredo wrote:
> UBSAN: shift-out-of-bounds in kernel/bpf/core.c:1414:2
> shift exponent 248 is too large for 32-bit type 'unsigned int'

I'm sorry, but I still do not understand what this changelog text means.

Please be very descriptive about what you are doing and why you are
doing it.  All that is here is a message from a random tool :(

thanks,
greg k-h
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2021-06-03  4:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000000000000c2987605be907e41@google.com>
2021-06-02 21:27 ` [PATCH v3] bpf: core: fix shift-out-of-bounds in ___bpf_prog_run Kurt Manucredo
2021-06-03  4:43   ` Greg KH [this message]
2021-06-05 15:01     ` [PATCH v4] " Kurt Manucredo
2021-06-05 17:55       ` Yonghong Song via Linux-kernel-mentees
2021-06-05 19:10         ` Alexei Starovoitov
2021-06-05 21:39           ` Yonghong Song via Linux-kernel-mentees
2021-06-06 19:44             ` Kurt Manucredo
2021-06-07  7:38           ` Dmitry Vyukov via Linux-kernel-mentees
2021-06-09 18:20             ` Kees Cook
2021-06-09 23:40               ` Yonghong Song via Linux-kernel-mentees
2021-06-10  5:32                 ` Dmitry Vyukov via Linux-kernel-mentees
2021-06-10  6:06                   ` Yonghong Song via Linux-kernel-mentees
2021-06-10 17:06                     ` Kees Cook
2021-06-10 17:52                       ` Alexei Starovoitov
2021-06-10 20:00                         ` Eric Biggers
2021-06-06 19:15         ` Kurt Manucredo

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=YLhd8BL3HGItbXmx@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=fuzzybritches0@gmail.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=syzbot+bed360704c521841c85d@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yhs@fb.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