From: ebiederm@xmission.com (Eric W. Biederman)
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: linux-next: manual merge of the userns tree with the tip tree
Date: Mon, 15 Oct 2018 00:49:49 -0500 [thread overview]
Message-ID: <87d0sbpxmq.fsf@xmission.com> (raw)
In-Reply-To: <20181015153437.70179aaf@canb.auug.org.au> (Stephen Rothwell's message of "Mon, 15 Oct 2018 15:34:37 +1100")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> On Mon, 15 Oct 2018 15:11:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Today's linux-next merge of the userns tree got a conflict in:
>>
>> arch/x86/mm/fault.c
>>
>> between commit:
>>
>> 164477c2331b ("x86/mm: Clarify hardware vs. software "error_code"")
>> (and others from that series)
>>
>> from the tip tree and commits:
>>
>> 768fd9c69bb5 ("signal/x86: Remove pkey parameter from bad_area_nosemaphore")
>> 25c102d803ea ("signal/x86: Remove pkey parameter from mm_fault_error")
>>
>> from the userns tree.
>>
>> I fixed it up (I think - see below) and can carry the fix as
>> necessary. This is now fixed as far as linux-next is concerned, but any
>> non trivial conflicts should be mentioned to your upstream maintainer
>> when your tree is submitted for merging. You may also want to consider
>> cooperating with the maintainer of the conflicting tree to minimise any
>> particularly complex conflicts.
>>
>> --
>> Cheers,
>> Stephen Rothwell
>>
>> diff --cc arch/x86/mm/fault.c
>> index c2e3e5127ebc,8d77700a7883..000000000000
>> --- a/arch/x86/mm/fault.c
>> +++ b/arch/x86/mm/fault.c
>> +/* Handle faults in the user portion of the address space */
>> +static inline
>> +void do_user_addr_fault(struct pt_regs *regs,
>> + unsigned long hw_error_code,
>> + unsigned long address)
>> +{
>> + unsigned long sw_error_code;
>> + struct vm_area_struct *vma;
>> + struct task_struct *tsk;
>> + struct mm_struct *mm;
>> + vm_fault_t fault, major = 0;
>> + unsigned int flags = FAULT_FLAG_ALLOW_RETRY | FAULT_FLAG_KILLABLE;
>> + u32 pkey;
>
> I missed removing the above line.
Yes. At first glance with the above change it looks like you got it.
Eric
next prev parent reply other threads:[~2018-10-15 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 4:11 linux-next: manual merge of the userns tree with the tip tree Stephen Rothwell
2018-10-15 4:34 ` Stephen Rothwell
2018-10-15 5:49 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 6:49 Stephen Rothwell
2020-12-11 7:24 Stephen Rothwell
2020-12-16 1:02 ` Stephen Rothwell
2018-09-24 3:34 Stephen Rothwell
2015-06-04 10:49 Stephen Rothwell
2012-05-21 7:30 Stephen Rothwell
2012-05-21 23:02 ` Eric W. Biederman
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=87d0sbpxmq.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).