linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	Mike Rapoport <rppt@kernel.org>
Subject: Re: mmotm 2020-11-16-16-47 uploaded (m/secretmem.c)
Date: Mon, 16 Nov 2020 20:20:12 -0800	[thread overview]
Message-ID: <e7cc79ce-2448-98bc-6ae9-306f6991986f@infradead.org> (raw)
In-Reply-To: <20201117004837.VMxSd_ozW%akpm@linux-foundation.org>

On 11/16/20 4:48 PM, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2020-11-16-16-47 has been uploaded to
> 
>    https://www.ozlabs.org/~akpm/mmotm/
> 
> mmotm-readme.txt says
> 
> README for mm-of-the-moment:
> 
> https://www.ozlabs.org/~akpm/mmotm/
> 
> This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> more than once a week.
> 
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> https://ozlabs.org/~akpm/mmotm/series
> 
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss.  Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
> 
> This tree is partially included in linux-next.  To see which patches are
> included in linux-next, consult the `series' file.  Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
> 
> 
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release.  Individual mmotm releases are tagged.  The master branch always
> points to the latest release, so it's constantly rebasing.
> 
> 	https://github.com/hnaz/linux-mm
> 
> The directory https://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> contains daily snapshots of the -mm tree.  It is updated more frequently
> than mmotm, and is untested.
> 


on x86_64:

as reported on 2020-11-12:

when CONFIG_MEMCG is not set:

../mm/secretmem.c: In function ‘secretmem_memcg_charge’:
../mm/secretmem.c:72:4: error: ‘struct page’ has no member named ‘memcg_data’
   p->memcg_data = page->memcg_data;
    ^~
../mm/secretmem.c:72:23: error: ‘struct page’ has no member named ‘memcg_data’
   p->memcg_data = page->memcg_data;
                       ^~
../mm/secretmem.c: In function ‘secretmem_memcg_uncharge’:
../mm/secretmem.c:86:4: error: ‘struct page’ has no member named ‘memcg_data’
   p->memcg_data = 0;
    ^~


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>


  reply	other threads:[~2020-11-17  4:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  0:48 mmotm 2020-11-16-16-47 uploaded akpm
2020-11-17  4:20 ` Randy Dunlap [this message]
2020-11-17  4:29   ` mmotm 2020-11-16-16-47 uploaded (m/secretmem.c) Stephen Rothwell

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=e7cc79ce-2448-98bc-6ae9-306f6991986f@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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