From: Jann Horn <jannh@google.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Konovalov <andreyknvl@gmail.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Christoph Lameter <cl@linux.com>,
David Rientjes <rientjes@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Marco Elver <elver@google.com>,
Pekka Enberg <penberg@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
kasan-dev@googlegroups.com
Subject: Re: [linux-next:master] [slub] d543c8fb9c: BUG_filp(Not_tainted):Bulk_free_expected#objects_but_found
Date: Wed, 31 Jul 2024 13:50:50 +0200 [thread overview]
Message-ID: <CAG48ez08Qzvqw+QA_kqm62+yqHeS0G+26C9jLeA7eYUqZMRkig@mail.gmail.com> (raw)
In-Reply-To: <202407311019.5ea52390-lkp@intel.com>
Hi!
On Wed, Jul 31, 2024 at 7:27 AM kernel test robot <oliver.sang@intel.com> wrote:
> hi, Jann Horn,
>
> we reported "WARNING:possible_circular_locking_dependency_detected"
> issue upon v3 of this patch in
> https://lore.kernel.org/all/202407291014.2ead1e72-oliver.sang@intel.com/
> several days ago.
>
> at that time, you said that real issue should be something like
> "BUG filp (Not tainted): Bulk free expected 1 objects but found 2"
> and you will send a fix.
>
> now we noticed this patch in in linux-next/master, but not sure the version.
>
> we found there are still similar issues so just send report to you FYI.
Right, that's still v2 of the patch - you can tell from the "Link:
https://lkml.kernel.org/r/20240724-kasan-tsbrcu-v2-2-45f898064468@google.com"
line in the commit message, which contains "v2" and links to an email
with subject "[PATCH v2 2/2] slub: Introduce CONFIG_SLUB_RCU_DEBUG".
And yeah, that seems like the same issue that I fixed in v4 of the
patch (https://lore.kernel.org/all/20240729-kasan-tsbrcu-v4-2-57ec85ef80c6@google.com/).
v5 is now in the mm tree, so I think once the next version of
linux-next is built, the issue should go away.
Have a nice day,
Jann
prev parent reply other threads:[~2024-07-31 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 5:27 kernel test robot
2024-07-31 11:50 ` Jann Horn [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=CAG48ez08Qzvqw+QA_kqm62+yqHeS0G+26C9jLeA7eYUqZMRkig@mail.gmail.com \
--to=jannh@google.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=cl@linux.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.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