linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Harry Yoo <harry.yoo@oracle.com>
Cc: Thomas Ballasi <tballasi@linux.microsoft.com>,
	linux-mm@kvack.org, linux-trace-kernel@vger.kernel.org,
	mhiramat@kernel.org, rostedt@goodmis.org
Subject: Re: build error on CONFIG_MEMCG=n "error: invalid use of undefined type 'struct mem_cgroup'"
Date: Tue, 6 Jan 2026 18:17:42 -0800	[thread overview]
Message-ID: <20260106181742.5d55894e50139fd7d64f6dcd@linux-foundation.org> (raw)
In-Reply-To: <aV29Xj2wo786xVn1@hyeyoo>

On Wed, 7 Jan 2026 10:56:46 +0900 Harry Yoo <harry.yoo@oracle.com> wrote:

> > --- a/include/trace/events/vmscan.h
> > +++ b/include/trace/events/vmscan.h
> > @@ -208,31 +215,34 @@ TRACE_EVENT(mm_shrink_slab_start,
> >  	TP_fast_assign(
> >  		__entry->shr = shr;
> >  		__entry->shrink = shr->scan_objects;
> > -		__entry->nid = sc->nid;
> >  		__entry->nr_objects_to_shrink = nr_objects_to_shrink;
> >  		__entry->gfp_flags = (__force unsigned long)sc->gfp_mask;
> >  		__entry->cache_items = cache_items;
> >  		__entry->delta = delta;
> >  		__entry->total_scan = total_scan;
> >  		__entry->priority = priority;
> > +		__entry->nid = sc->nid;
> > +		__entry->memcg_id = sc->memcg ? cgroup_id(sc->memcg->css.cgroup) : 0;
> 
> Hi Thomas, this is breaking CONFIG_MEMCG=n builds.

yup, thanks, that series has been removed from mm.git.

  reply	other threads:[~2026-01-07  2:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 18:14 [PATCH 0/2] mm: vmscan: add PID and cgroup ID to vmscan tracepoints Thomas Ballasi
2025-12-08 18:14 ` [PATCH 1/2] mm: vmscan: add cgroup IDs " Thomas Ballasi
2025-12-08 18:14 ` [PATCH 2/2] mm: vmscan: add PIDs " Thomas Ballasi
2025-12-10  3:09   ` Steven Rostedt
2025-12-16 14:02 ` [PATCH v2 0/2] mm: vmscan: add PID and cgroup ID " Thomas Ballasi
2025-12-16 14:02   ` [PATCH v2 1/2] mm: vmscan: add cgroup IDs " Thomas Ballasi
2025-12-16 18:50     ` Shakeel Butt
2025-12-17 22:21     ` Steven Rostedt
2025-12-16 14:02   ` [PATCH v2 2/2] mm: vmscan: add PIDs " Thomas Ballasi
2025-12-16 18:03     ` Steven Rostedt
2025-12-29 10:54       ` Thomas Ballasi
2025-12-29 18:29         ` Steven Rostedt
2025-12-29 21:36           ` Steven Rostedt
2026-01-05 16:04   ` [PATCH v3 0/2] mm: vmscan: add PID and cgroup ID " Thomas Ballasi
2026-01-05 16:04     ` [PATCH v3 1/2] mm: vmscan: add cgroup IDs " Thomas Ballasi
2026-01-05 22:46       ` Shakeel Butt
2026-01-07 18:14         ` Shakeel Butt
2026-01-07 18:32           ` Andrew Morton
2026-01-07 20:35             ` Shakeel Butt
2026-01-07  1:56       ` build error on CONFIG_MEMCG=n "error: invalid use of undefined type 'struct mem_cgroup'" Harry Yoo
2026-01-07  2:17         ` Andrew Morton [this message]
2026-01-05 16:04     ` [PATCH v3 2/2] mm: vmscan: add PIDs to vmscan tracepoints Thomas Ballasi
2026-01-06  2:06     ` [PATCH v3 0/2] mm: vmscan: add PID and cgroup ID " Andrew Morton
2026-01-06  2:21       ` Steven Rostedt

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=20260106181742.5d55894e50139fd7d64f6dcd@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=harry.yoo@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tballasi@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).