From: Namhyung Kim <namhyung@kernel.org>
To: Song Liu <song@kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
bpf@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, Arnaldo Carvalho de Melo <acme@kernel.org>,
Kees Cook <kees@kernel.org>
Subject: Re: [PATCH v4 bpf-next 1/3] bpf: Add kmem_cache iterator
Date: Fri, 4 Oct 2024 14:42:14 -0700 [thread overview]
Message-ID: <ZwBhNqXbn5R1JN1Y@google.com> (raw)
In-Reply-To: <CAPhsuW5BKxZH2EA=fuQa_3man5_qcUt3euwtfwsqD4g36JngaA@mail.gmail.com>
On Fri, Oct 04, 2024 at 01:45:09PM -0700, Song Liu wrote:
> On Wed, Oct 2, 2024 at 11:09 AM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> [...]
> > +
> > +static void *kmem_cache_iter_seq_start(struct seq_file *seq, loff_t *pos)
> > +{
> > + loff_t cnt = 0;
> > + bool found = false;
> > + struct kmem_cache *s;
> > +
> > + mutex_lock(&slab_mutex);
> > +
> > + /*
> > + * Find an entry at the given position in the slab_caches list instead
> > + * of keeping a reference (of the last visited entry, if any) out of
> > + * slab_mutex. It might miss something if one is deleted in the middle
> > + * while it releases the lock. But it should be rare and there's not
> > + * much we can do about it.
> > + */
> > + list_for_each_entry(s, &slab_caches, list) {
> > + if (cnt == *pos) {
> > + /*
> > + * Make sure this entry remains in the list by getting
> > + * a new reference count. Note that boot_cache entries
> > + * have a negative refcount, so don't touch them.
> > + */
> > + if (s->refcount > 0)
> > + s->refcount++;
> > + found = true;
> > + break;
> > + }
> > + cnt++;
> > + }
> > + mutex_unlock(&slab_mutex);
> > +
> > + if (!found)
> > + return NULL;
> > +
> > + ++*pos;
>
> This should be
>
> if (*pos == 0)
> ++*pos;
Oh, I thought there's check for seq->count after the seq->op->show()
for the ->start(). I need to check this logic again, thanks for
pointing this out.
Thanks,
Namhyung
>
> > + return s;
> > +}
> > +
> > +static void kmem_cache_iter_seq_stop(struct seq_file *seq, void *v)
> [...]
next prev parent reply other threads:[~2024-10-04 21:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 18:09 [PATCH v4 bpf-next 0/3] bpf: Add kmem_cache iterator and kfunc Namhyung Kim
2024-10-02 18:09 ` [PATCH v4 bpf-next 1/3] bpf: Add kmem_cache iterator Namhyung Kim
2024-10-03 7:35 ` Vlastimil Babka
2024-10-04 20:33 ` Song Liu
2024-10-04 21:37 ` Namhyung Kim
2024-10-04 21:46 ` Song Liu
2024-10-04 23:29 ` Namhyung Kim
2024-10-04 20:45 ` Song Liu
2024-10-04 21:42 ` Namhyung Kim [this message]
2024-10-02 18:09 ` [PATCH v4 bpf-next 2/3] mm/bpf: Add bpf_get_kmem_cache() kfunc Namhyung Kim
2024-10-04 5:31 ` Namhyung Kim
2024-10-04 20:10 ` Song Liu
2024-10-04 21:25 ` Roman Gushchin
2024-10-04 21:36 ` Song Liu
2024-10-04 21:58 ` Namhyung Kim
2024-10-04 22:57 ` Song Liu
2024-10-04 23:28 ` Namhyung Kim
2024-10-04 23:44 ` Alexei Starovoitov
2024-10-04 23:56 ` Song Liu
2024-10-06 19:00 ` Namhyung Kim
2024-10-07 12:57 ` Vlastimil Babka
2024-10-09 7:17 ` Namhyung Kim
2024-10-10 16:46 ` Namhyung Kim
2024-10-10 17:04 ` Alexei Starovoitov
2024-10-10 22:56 ` Namhyung Kim
2024-10-02 18:09 ` [PATCH v4 bpf-next 3/3] selftests/bpf: Add a test for kmem_cache_iter Namhyung Kim
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=ZwBhNqXbn5R1JN1Y@google.com \
--to=namhyung@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.lau@linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vbabka@suse.cz \
--cc=yonghong.song@linux.dev \
/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