linux-hexagon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "broonie@kernel.org" <broonie@kernel.org>
Cc: "Schimpe, Christina" <christina.schimpe@intel.com>,
	"Yang, Weijiang" <weijiang.yang@intel.com>,
	"hjl.tools@gmail.com" <hjl.tools@gmail.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"monstr@monstr.eu" <monstr@monstr.eu>,
	"rppt@kernel.org" <rppt@kernel.org>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>,
	"Torvalds, Linus" <torvalds@linux-foundation.org>,
	"kirill.shutemov@linux.intel.com"
	<kirill.shutemov@linux.intel.com>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"dinguyen@kernel.org" <dinguyen@kernel.org>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>, arnd@
Subject: Re: [PATCH v9 01/42] mm: Rename arch pte_mkwrite()'s to pte_mkwrite_novma()
Date: Mon, 17 Jul 2023 15:55:50 +0000	[thread overview]
Message-ID: <87acbb49fa83b0e3f261315a531e105da9e5b9d6.camel@intel.com> (raw)
In-Reply-To: <b389274a-abed-40dc-8e33-7ce922ea9b61@sirena.org.uk>

On Fri, 2023-07-14 at 23:57 +0100, Mark Brown wrote:
> On Mon, Jun 12, 2023 at 05:10:27PM -0700, Rick Edgecombe wrote:
> > The x86 Shadow stack feature includes a new type of memory called
> > shadow
> > stack. This shadow stack memory has some unusual properties, which
> > requires
> > some core mm changes to function properly.
> 
> This seems to break sparc64_defconfig when applied on top of v6.5-
> rc1:
> 
> In file included from /home/broonie/git/bisect/include/linux/mm.h:29,
>                  from /home/broonie/git/bisect/net/core/skbuff.c:40:
> /home/broonie/git/bisect/include/linux/pgtable.h: In function
> 'pmd_mkwrite':
> /home/broonie/git/bisect/include/linux/pgtable.h:528:9: error:
> implicit declaration of function 'pmd_mkwrite_novma'; did you mean
> 'pte_mkwrite_novma'? [-Werror=implicit-function-declaration]
>   return pmd_mkwrite_novma(pmd);
>          ^~~~~~~~~~~~~~~~~
>          pte_mkwrite_novma
> /home/broonie/git/bisect/include/linux/pgtable.h:528:9: error:
> incompatible types when returning type 'int' but 'pmd_t' {aka 'struct
> <anonymous>'} was expected
>   return pmd_mkwrite_novma(pmd);
>          ^~~~~~~~~~~~~~~~~~~~~~
> 
> The same issue seems to apply with the version that was in -next
> based
> on v6.4-rc4 too.

The version in your branch is not the same as the version in tip (which
had a squashed build fix). I was able to reproduce the build error with
your branch. But not with the one in tip rebased on v6.5-rc1. So can
you try this version:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/shstk&id=899223d69ce9f338056f4c41ef870d70040fc860



  reply	other threads:[~2023-07-17 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230613001108.3040476-1-rick.p.edgecombe@intel.com>
2023-06-13  0:10 ` [PATCH v9 01/42] mm: Rename arch pte_mkwrite()'s to pte_mkwrite_novma() Rick Edgecombe
2023-06-13  7:19   ` Geert Uytterhoeven
2023-06-13 16:14     ` Edgecombe, Rick P
2023-06-13  7:43   ` Mike Rapoport
     [not found]     ` <20230613074347.GR52412-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2023-06-13 16:14       ` Edgecombe, Rick P
2023-06-13 12:26   ` David Hildenbrand
2023-06-13 16:14     ` Edgecombe, Rick P
2023-07-14 22:57   ` Mark Brown
2023-07-17 15:55     ` Edgecombe, Rick P [this message]
     [not found]       ` <87acbb49fa83b0e3f261315a531e105da9e5b9d6.camel-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2023-07-17 16:51         ` Mark Brown

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=87acbb49fa83b0e3f261315a531e105da9e5b9d6.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=broonie@kernel.org \
    --cc=christina.schimpe@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dinguyen@kernel.org \
    --cc=hjl.tools@gmail.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=monstr@monstr.eu \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=weijiang.yang@intel.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).