linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: ffhgfv <744439878@qq.com>
Cc: minchan <minchan@kernel.org>,
	senozhatsky <senozhatsky@chromium.org>,
	 akpm <akpm@linux-foundation.org>, linux-mm <linux-mm@kvack.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel bug found and suggestions for fixing it
Date: Thu, 6 Mar 2025 00:29:37 +0900	[thread overview]
Message-ID: <hom2of3ookiuoizx6r6ye3fixnhimcl7kxpqk6kebhyzul2hmk@3h3nkrvpfddo> (raw)
In-Reply-To: <tencent_6BF1F231EF7277B8B3EDF3999FC8CCB53B09@qq.com>

On (25/03/05 09:49), ffhgfv wrote:
> Hello, I found a bug titled "  BUG: corrupted list in fix_fullness_group "
> with modified syzkaller in the lasted upstream related to  ZSMALLOC.
[..]
> static int fix_fullness_group(struct size_class *class, struct zspage *zspage)
> {
> 	int newfg;
> 
> 	newfg = get_fullness_group(class, zspage);
> 	if (newfg == zspage-&gt;fullness)
> 		goto out;
> ++  spin_lock(&amp;class-&gt;lock);
> 	remove_zspage(class, zspage);
> 	insert_zspage(class, zspage, newfg);
> ++  spin_unlock(&amp;class-&gt;lock);
> out:
> 	return newfg;
> }

fix_fullness_group() is *always* called under class->lock.
zs_malloc() calls it under class->lock, so does  zs_free().


      parent reply	other threads:[~2025-03-05 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 14:49 =?gb18030?B?ZmZoZ2Z2?=
2025-03-05 15:03 ` =?gb18030?B?u9i4tKO6a2VybmVsIGJ1ZyBmb3VuZCBhbmQgc3VnZ2VzdGlvbnMgZm9yIGZpeGluZyBpdA==?= =?gb18030?B?ZmZoZ2Z2?=
2025-03-05 15:29 ` Sergey Senozhatsky [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=hom2of3ookiuoizx6r6ye3fixnhimcl7kxpqk6kebhyzul2hmk@3h3nkrvpfddo \
    --to=senozhatsky@chromium.org \
    --cc=744439878@qq.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox