The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	amd-gfx@lists.freedesktop.org, Duncan <1i5t5.duncan@cox.net>,
	Anthony Ruhier <anthony.ruhier@gmail.com>,
	Vinicius <mphantomx@yahoo.com.br>,
	Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: [Regression] hangs caused by commit 3202fa62fb (slub: relocate freelist pointer to middle of object)
Date: Tue, 21 Jul 2020 12:00:36 -0700	[thread overview]
Message-ID: <202007211156.D8BEDEA247@keescook> (raw)
In-Reply-To: <15cbac6d-1f96-2ba9-cb54-08af6682f56d@molgen.mpg.de>

On Tue, Jul 21, 2020 at 04:55:12PM +0200, Paul Menzel wrote:
> No idea, if you are aware of it yet, but three people verified that commit
> 3202fa62fb (slub: relocate freelist pointer to middle of object) causes a
> regression on AMD hardware [1].

Hi, thanks for emailing; I don't get bugzilla notifications, so I hadn't
seen this yet.

> It’d be great, if you took a look, and advised if this commit (and
> follow-ups) should be reverted, until the issue is analyzed.

There have been a number of fixes to that commit (which I see are
mentioned in a quick skim of the bug), but they've mostly been around
additional slab debugging features. If it's causing a problem outside
of that, my instinct would be there might be a use-after-free happening,
but I'll go read the bug more closely now, and comment there (or here,
if needed).

Thanks!

-- 
Kees Cook

      reply	other threads:[~2020-07-21 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 14:55 [Regression] hangs caused by commit 3202fa62fb (slub: relocate freelist pointer to middle of object) Paul Menzel
2020-07-21 19:00 ` 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=202007211156.D8BEDEA247@keescook \
    --to=keescook@chromium.org \
    --cc=1i5t5.duncan@cox.net \
    --cc=akpm@linux-foundation.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=anthony.ruhier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mphantomx@yahoo.com.br \
    --cc=pmenzel@molgen.mpg.de \
    --cc=regressions@leemhuis.info \
    /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