linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@intel.com>
To: "V, Narasimhan" <Narasimhan.V@amd.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: WARNING: CPU: 43 PID: 2254 at mm/slub.c:4655 krealloc_noprof+0x2c7/0x300 with next-20241003
Date: Mon, 14 Oct 2024 12:38:39 +0800	[thread overview]
Message-ID: <ZwygTwPVaKs5qzGN@feng-clx.sh.intel.com> (raw)
In-Reply-To: <DM4PR12MB50868A0BEFA31FCFB1FA440C897D2@DM4PR12MB5086.namprd12.prod.outlook.com>

Hi,

Thanks for sharing the config!

On Mon, Oct 07, 2024 at 06:35:42AM +0000, V, Narasimhan wrote:
> >> Hi,
> >>
> >> Seeing the following bug on boot with next-20241003
> 
> > I think it is caused by my commit d0a38fad51cc "mm/slub: Improve redzone check and zeroing for > krealloc()"
> > that the virt_to_cache() it calls returns NULL
> 
> > Could you share your kernel config? Is KFENCE enabled?
> 
> Yes, KFENCE is enabled.
> 
> Here is the kernel config used.

> CONFIG_HAVE_ARCH_KASAN=y
> CONFIG_HAVE_ARCH_KASAN_VMALLOC=y
> CONFIG_CC_HAS_KASAN_GENERIC=y
> CONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=y
> # CONFIG_KASAN is not set
> CONFIG_HAVE_ARCH_KFENCE=y
> CONFIG_KFENCE=y


> CONFIG_KFENCE_SAMPLE_INTERVAL=0

I think this effectively disables the kfence, so it should
be the large kmalloc case, as Vlastimil said in the other
mail.

We will try to address it in v3 patches.

Thanks,
Feng

> CONFIG_KFENCE_NUM_OBJECTS=255
> # CONFIG_KFENCE_DEFERRABLE is not set
> # CONFIG_KFENCE_STATIC_KEYS is not set
> CONFIG_KFENCE_STRESS_TEST_FAULTS=0
> CONFIG_HAVE_ARCH_KMSAN=y
> # end of Memory Debugging
> 


  reply	other threads:[~2024-10-14  4:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04  6:22 V, Narasimhan
2024-10-04 10:17 ` Feng Tang
2024-10-04 14:17   ` Vlastimil Babka
2024-10-07  6:35   ` V, Narasimhan
2024-10-14  4:38     ` Feng Tang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-04  6:06 V, Narasimhan

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=ZwygTwPVaKs5qzGN@feng-clx.sh.intel.com \
    --to=feng.tang@intel.com \
    --cc=Narasimhan.V@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.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