mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>,
	"Vlastimil Babka" <vbabka@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	linux- stable <stable@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	ndesaulniers@google.com, rientjes@google.com,
	Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: Stable backport request: skbuff: Proactively round up to kmalloc bucket size
Date: Wed, 24 May 2023 06:51:52 -0700	[thread overview]
Message-ID: <5A79C566-3213-456A-8CA3-8F0F1A2D9781@kernel.org> (raw)
In-Reply-To: <CAEUSe794ifGiY9tsXfnqDsDSJ+UOOB1kJrm1Jb8kZ5fsoBZ5Sg@mail.gmail.com>

On May 23, 2023 8:52:53 PM PDT, "Daniel Díaz" <daniel.diaz@linaro.org> wrote:
>Hello!
>
>On Tue, 23 May 2023 at 00:28, Vlastimil Babka <vbabka@suse.cz> wrote:
>> On 5/22/23 20:23, Daniel Díaz wrote:
>> > Hello!
>> >
>> > Would the stable maintainers please consider backporting the following
>> > commit to the 6.1? We are trying to build gki_defconfig (plus a few
>> > extras) on Arm64 and test it under Qemu-arm64, but it fails to boot.
>> > Bisection has pointed here.
>>
>> You mean the bisection was done to find the first "good" commit between 6.1
>> and e.g. 6.3?
>>
>> As others said, this commit wasn't expected to be a fix to a known bug.
>> Maybe you found one that we didn't know of, or it might be accidentaly
>> masking some other bug.
>
>How interesting! Yes, we happened to run a bisection between v6.1 and
>v6.3 and we found where it started working with the following
>configuration:
>  https://storage.tuxsuite.com/public/linaro/daniel/builds/2QA2CHQUpqKe27FyMZrBNILVwXi/config

Ah yes, from CONFIG_UBSAN_BOUNDS=y and CONFIG_UBSAN_TRAP=y

This was a known issue in upstream, oddly only exposed on arm64. Something re-broke with __alloc_size after commit 93dd04ab0b2b had tried to work around it. I didn't think any kernel released with this broken, though, so perhaps what broke it got added to -stable?

>With that patch on top of v6.1.29 it boots fine under Qemu-arm64; as
>v6.1.y stands, it panics with this:

It should be fine to backport the patch, IMO.


-- 
Kees Cook

      reply	other threads:[~2023-05-24 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 18:23 Daniel Díaz
2023-05-22 18:29 ` Greg Kroah-Hartman
2023-05-22 18:37 ` Nick Desaulniers
2023-05-24  3:45   ` Daniel Díaz
2023-05-23  6:28 ` Vlastimil Babka
2023-05-24  3:52   ` Daniel Díaz
2023-05-24 13:51     ` Kees Cook [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=5A79C566-3213-456A-8CA3-8F0F1A2D9781@kernel.org \
    --to=kees@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rientjes@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=vbabka@suse.cz \
    /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

all inboxes | Powered by JetHome®