All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tong Tiangen <tongtiangen@huawei.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>, <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [RFC PATCH -next V2 1/7] x86: fix copy_mc_to_user compile error
Date: Wed, 6 Apr 2022 18:02:15 +0800	[thread overview]
Message-ID: <99acc7d2-a11b-250b-f614-18077fb76cc0@huawei.com> (raw)
In-Reply-To: <Yk1bu88TcjXw/iU4@zn.tnic>



在 2022/4/6 17:22, Borislav Petkov 写道:
> On Wed, Apr 06, 2022 at 09:13:05AM +0000, Tong Tiangen wrote:
>> The follow patch
> 
> There's no concept of "follow patch" in git - you need to explain this
> differently.
> 
>> will add copy_mc_to_user to include/linux/uaccess.h, X86
>> must declare Implemented to avoid compile error.
> 
> I don't know what that means. Try again pls.
> 

This description is not good, will redescribe it in next version.

Here I describe the reasons for this:

Patch 3/7 in patchset[1] introduce copy_mc_to_user() in 
include/linux/uaccess.h and the prototype is:

     static inline unsigned long __must_check
     copy_mc_to_user(void *dst, const void *src, size_t cnt)

The prototype in x86 is:

     unsigned long __must_check
     copy_mc_to_user(void *to, const void *from, unsigned len);

This two are a little different, so I added the follow code to x86 to
avoid prototype conflict compile error.

     #define copy_mc_to_user copy_mc_to_user

In addition, I think this #define should be added here.

[1]https://patchwork.kernel.org/project/linux-mm/cover/20220406091311.3354723-1-tongtiangen@huawei.com/

Thanks.
Tong.

WARNING: multiple messages have this Message-ID (diff)
From: Tong Tiangen <tongtiangen@huawei.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>, <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [RFC PATCH -next V2 1/7] x86: fix copy_mc_to_user compile error
Date: Wed, 6 Apr 2022 18:02:15 +0800	[thread overview]
Message-ID: <99acc7d2-a11b-250b-f614-18077fb76cc0@huawei.com> (raw)
In-Reply-To: <Yk1bu88TcjXw/iU4@zn.tnic>



在 2022/4/6 17:22, Borislav Petkov 写道:
> On Wed, Apr 06, 2022 at 09:13:05AM +0000, Tong Tiangen wrote:
>> The follow patch
> 
> There's no concept of "follow patch" in git - you need to explain this
> differently.
> 
>> will add copy_mc_to_user to include/linux/uaccess.h, X86
>> must declare Implemented to avoid compile error.
> 
> I don't know what that means. Try again pls.
> 

This description is not good, will redescribe it in next version.

Here I describe the reasons for this:

Patch 3/7 in patchset[1] introduce copy_mc_to_user() in 
include/linux/uaccess.h and the prototype is:

     static inline unsigned long __must_check
     copy_mc_to_user(void *dst, const void *src, size_t cnt)

The prototype in x86 is:

     unsigned long __must_check
     copy_mc_to_user(void *to, const void *from, unsigned len);

This two are a little different, so I added the follow code to x86 to
avoid prototype conflict compile error.

     #define copy_mc_to_user copy_mc_to_user

In addition, I think this #define should be added here.

[1]https://patchwork.kernel.org/project/linux-mm/cover/20220406091311.3354723-1-tongtiangen@huawei.com/

Thanks.
Tong.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-06 13:37 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  9:13 [RFC PATCH -next V2 0/7]arm64: add machine check safe support Tong Tiangen
2022-04-06  9:13 ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 1/7] x86: fix copy_mc_to_user compile error Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06  9:22   ` Borislav Petkov
2022-04-06  9:22     ` Borislav Petkov
2022-04-06 10:02     ` Tong Tiangen [this message]
2022-04-06 10:02       ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 2/7] arm64: fix page_address return value in copy_highpage Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06 10:22   ` Mark Rutland
2022-04-06 10:22     ` Mark Rutland
2022-04-06 12:47     ` Tong Tiangen
2022-04-06 12:47       ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 3/7] arm64: add support for machine check error safe Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06 10:58   ` Mark Rutland
2022-04-06 10:58     ` Mark Rutland
2022-04-07 14:26     ` Tong Tiangen
2022-04-07 14:26       ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 4/7] arm64: add copy_from_user to machine check safe Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06 11:19   ` Mark Rutland
2022-04-06 11:19     ` Mark Rutland
2022-04-07 14:28     ` Tong Tiangen
2022-04-07 14:28       ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 5/7] arm64: add get_user " Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06 11:22   ` Mark Rutland
2022-04-06 11:22     ` Mark Rutland
2022-04-07 14:38     ` Tong Tiangen
2022-04-07 14:38       ` Tong Tiangen
2022-04-08 15:22       ` Mark Rutland
2022-04-08 15:22         ` Mark Rutland
2022-04-09  9:17         ` Tong Tiangen
2022-04-09  9:17           ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 6/7] arm64: add cow " Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06  9:13 ` [RFC PATCH -next V2 7/7] arm64: add pagecache reading " Tong Tiangen
2022-04-06  9:13   ` Tong Tiangen
2022-04-06 11:27   ` Mark Rutland
2022-04-06 11:27     ` Mark Rutland
2022-04-07 14:56     ` Tong Tiangen
2022-04-07 14:56       ` Tong Tiangen
2022-04-07 15:53       ` Robin Murphy
2022-04-07 15:53         ` Robin Murphy
2022-04-08  2:43         ` Tong Tiangen
2022-04-08  2:43           ` Tong Tiangen
2022-04-08 11:11           ` Robin Murphy
2022-04-08 11:11             ` Robin Murphy
2022-04-09  9:24             ` Tong Tiangen
2022-04-09  9:24               ` Tong Tiangen
2022-04-06 10:04 ` [RFC PATCH -next V2 0/7]arm64: add machine check safe support Mark Rutland
2022-04-06 10:04   ` Mark Rutland
2022-04-07  4:21   ` Tong Tiangen
2022-04-07  4:21     ` Tong Tiangen

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=99acc7d2-a11b-250b-f614-18077fb76cc0@huawei.com \
    --to=tongtiangen@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.