All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 204371] BUG kmalloc-4k (Tainted: G        W        ): Object padding overwritten
Date: Thu, 01 Aug 2019 12:47:19 +0000	[thread overview]
Message-ID: <bug-204371-206035-FJ4o58Kg5c@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204371-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=204371

--- Comment #5 from Erhard F. (erhard_f@mailbox.org) ---
On Wed, 31 Jul 2019 12:09:54 +0000
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=204371
> 
> --- Comment #4 from mpe@ellerman.id.au ---
>
> > I suspect proc_cgroup_show() is innocent and that perhaps
> > bpf_prepare_filter() had a memory scribble.  iirc there has been at
> > least one recent pretty serious bpf fix applied recently.  Can others
> > please take a look?  
> 
> I haven't been able to reproduce this on a 64-bit or 32-bit powerpc
> machine here. But I don't run gentoo userspace, so I suspect I'm not
> tripping the same path at boot. I did run the seccomp selftest and that
> didn't trip it either.
> 
> cheers

Doing some fiddling around on another bug (bug #204375), I noticed that I get
this "kmalloc-4k (Tainted: G W ): Object padding overwritten" during boot only
when I boot from my btrfs partition, but not from my other ext4 partition. The
ext4 partition is not a clone, but pretty much the same stuff in the same
versions. My btrfs root is mounted with 'lazytime,compress=zstd:1', systemd is
242.

I built a 5.2.5 kernel on the Talos II with CONFIG_SLUB_DEBUG=y but here I
don't hit the bug, even if I boot from a btrfs partition with the same
settings. Have to test it on the G5 yet (kernel .config more similar to the G4
one than the Talos II one).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-08-01 12:50 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-204371-206035@https.bugzilla.kernel.org/>
2019-07-29 23:28 ` [Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten bugzilla-daemon
2019-07-30 18:52 ` bugzilla-daemon
2019-07-31 12:00   ` Michael Ellerman
2019-08-17  8:09   ` christophe leroy
2019-07-31  9:03 ` bugzilla-daemon
2019-07-31 12:09 ` bugzilla-daemon
2019-08-01 12:47 ` bugzilla-daemon [this message]
2019-08-06 20:47 ` bugzilla-daemon
2019-08-06 20:48 ` bugzilla-daemon
2019-08-06 20:51 ` bugzilla-daemon
2019-08-08 10:53 ` bugzilla-daemon
2019-08-08 11:26 ` bugzilla-daemon
2019-08-09 12:31   ` Michael Ellerman
2019-08-09 12:31     ` Michael Ellerman
2019-08-09 12:31 ` bugzilla-daemon
2019-08-11 20:03 ` bugzilla-daemon
2019-08-11 21:18 ` bugzilla-daemon
2019-08-13  9:19 ` bugzilla-daemon
2019-08-13  9:20 ` bugzilla-daemon
2019-08-13 15:38 ` bugzilla-daemon
2019-08-14  8:56 ` bugzilla-daemon
2019-08-14 15:12 ` bugzilla-daemon
2019-08-14 16:10 ` bugzilla-daemon
2019-08-14 17:44 ` bugzilla-daemon
2019-08-14 17:45 ` bugzilla-daemon
2019-08-14 17:48 ` bugzilla-daemon
2019-08-14 17:53 ` bugzilla-daemon
2019-08-14 20:28 ` bugzilla-daemon
2019-08-14 20:33 ` bugzilla-daemon
2019-08-15 14:38 ` bugzilla-daemon
2019-08-15 16:45 ` bugzilla-daemon
2019-08-15 17:07 ` bugzilla-daemon
2019-08-15 17:11 ` bugzilla-daemon
2019-08-15 17:56 ` bugzilla-daemon
2019-08-15 18:33 ` bugzilla-daemon
2019-08-16  8:22 ` bugzilla-daemon
2019-08-16 14:35 ` bugzilla-daemon
2019-08-16 14:38 ` bugzilla-daemon
2019-08-16 15:20 ` bugzilla-daemon
2019-08-16 18:02 ` bugzilla-daemon
2019-08-16 20:51 ` bugzilla-daemon
2019-08-17  8:09 ` bugzilla-daemon
2019-08-22 13:39 ` bugzilla-daemon
     [not found] <bug-204371-206129@https.bugzilla.kernel.org/>
     [not found] ` <bug-204371-206129-GvRQpDzlfW@https.bugzilla.kernel.org/>
2019-08-16 14:59   ` Christophe Leroy

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=bug-204371-206035-FJ4o58Kg5c@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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.