linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: geng sun <sun.gengeration.sun@gmail.com>
To: Xiongwei Song <sxwjean@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: An variable used before init
Date: Mon, 13 Nov 2023 16:55:54 +0800	[thread overview]
Message-ID: <38C0C09C-1B96-4090-9A71-25D416561956@gmail.com> (raw)
In-Reply-To: <CAEVVKH_fH7Nc+ieON7Lwd1L_fMomq11y4_4xuiYCz2EA52mAnA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]


Thank you for your explanation. Iunderstand. Thank you very much.

> On Nov 13, 2023, at 09:36, Xiongwei Song <sxwjean@gmail.com> wrote:
> 
> Hi,
> 
> You can see the definition of struct slab, the counters uses same space
> with inuse, objects and frozen because they are in a union. So when
> counters gets a value, the other 3 members also get a value.
> 
> struct slab {
> ......snip......
>                                        union {
>                                                unsigned long counters;
>                                                struct {
>                                                        unsigned inuse:16;
>                                                        unsigned objects:15;
>                                                        unsigned frozen:1;
>                                                };
>                                        };
> ......snip......
> }
> 
> Regards,
> Xiongwei
> 
>> On Sun, Nov 12, 2023 at 5:55 AM geng sun <sun.gengeration.sun@gmail.com> wrote:
>> 
>> Hi linux-mm
>> 
>> I find one odd variable “new” in slub, it was used before init.
>> Maybe the value in new was undefined.
>> And I can not understand how it work.
>> Could you explain this code for me?
>> Thanks.
>> 
>> Best regards.
>> static void __slab_free(struct kmem_cache *s, struct page *page,
>> void *head, void *tail, int cnt,
>> unsigned long addr)
>> 
>> {
>> void *prior;
>> int was_frozen;
>> struct page new;
>> unsigned long counters;
>> struct kmem_cache_node *n = NULL;
>> unsigned long flags;
>> stat(s, FREE_SLOWPATH);
>> if (kmem_cache_debug(s) &&
>> !free_debug_processing(s, page, head, tail, cnt, addr))
>> return;
>> 
>> do {
>> if (unlikely(n)) {
>> spin_unlock_irqrestore(&n->list_lock, flags);
>> n = NULL;
>> }
>> prior = page->freelist;
>> counters = page->counters;
>> set_freepointer(s, tail, prior);
>> new.counters = counters;
>> was_frozen = new.frozen;
>> new.inuse -= cnt;
>> if ((!new.inuse || !prior) && !was_frozen) {

[-- Attachment #2: Type: text/html, Size: 10854 bytes --]

      reply	other threads:[~2023-11-13  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 15:42 geng sun
2023-11-13  1:35 ` Xiongwei Song
2023-11-13  8:55   ` geng sun [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=38C0C09C-1B96-4090-9A71-25D416561956@gmail.com \
    --to=sun.gengeration.sun@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=sxwjean@gmail.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