Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp273995ybi; Wed, 29 May 2019 21:09:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqzivhnkWaY2+PqmYZNjBWGoEDtF/3WDAKaxM4k5MRAlxjstzKomKeS9vqJM/HFElGqnC+Zy X-Received: by 2002:a63:ff23:: with SMTP id k35mr1854494pgi.139.1559189350426; Wed, 29 May 2019 21:09:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559189350; cv=none; d=google.com; s=arc-20160816; b=GKecLhuZPMnXW1MLunyMhp8ZCqU8n/QZHkbBGrkVgMcfFfOHKtyB+qr+QTmSjHxjx9 XxeNkBXuYQKFrTTIWSQ1z5TpLBRHpJMLOxpQS5p6+DvB9sEQ+JYg3T/LyqIM5fjsXArV NPsraBFO54wzoeB17Dn0QMEUuEaiaDWX4PVEpgH15yjpXY+02oWoooJBzxWJaACT2WDq jjQCUpQtGvOey6arDQoO7yhD/uBZc2FzsSJ5PJ1ht3bPONLZgHjOfsBYM1I/mVTQ/ndE V2uwr+SFXb6xBr8rgLHQR1b6tj4sK01Vjj3zBje4xFJsmeUjesEaU9x1Rt4YnwVS0RcU OKnA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:subject:cc:to :from:date:dkim-signature; bh=va4DqsaRsBhtA8BtSoGFRYMC6pCRBNdeDL3m1vPkRMk=; b=CISdSeAVKP+WsH0SHlfmcCK6ODiFyNkzjSqm2MwHr4mWYjLGMRyXJYlEMLuiVzFRiQ yPjfNSchkxsOya5Ixqo+1EQfUXBn2GQ2aDEY8QFwkNIE0h+ZKATTLk/RodycX2p8U6Fv dWKsQQkX446k6qbpbggpo6REueDzSAIiqqCAytOrivdxMCSs9Av/DjoCyAeg+fquspxT S6NpPd1z5Fk4NsGHtKyTcicYdykmvGFqIhudbBRW1bm6Q0+7mKvXhPdi6B9IZE3d+YPV KbWmtV5sajYldse0/GIq5AjZYVp78+/J4kiVqFPb5vJGrMoOQCRUCkI0NWfBow+XvId7 ovmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=vGCwgvCr; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l2si1694287pje.54.2019.05.29.21.08.54; Wed, 29 May 2019 21:09:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=vGCwgvCr; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727132AbfE3EHw (ORCPT + 99 others); Thu, 30 May 2019 00:07:52 -0400 Received: from bilbo.ozlabs.org ([203.11.71.1]:43845 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731084AbfE3DRZ (ORCPT ); Wed, 29 May 2019 23:17:25 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 45Dt6n5N36z9sQr; Thu, 30 May 2019 13:17:21 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1559186242; bh=9+KNxKl040dLwGXZ8/yu2FEkk+iG0IsjYZFOHUKcuRA=; h=Date:From:To:Cc:Subject:From; b=vGCwgvCrGbi8kUfybY6qOeaGw3gfTGVIT8rEt4UPomauQWv181+NLL04TfzN5TXqq merrCo6EvDiX5DmvvtMzfXI4Q2rROxjGD45w+ksoTO/b51ssEyIJz+z098d+BdqqVB wirJnpyma6zcPOyVSqzeUFHEamKtIFqhKpNkXgK0VWRWJQ751i1zMGYvHvktzmOC2v I0klK38eCkHCwMlCFqe+u4w008uXBAxztBXSAxvqvraIPv6RNo/0M1LnVWzpq80CE+ zXDqaaC/1/myHKROvLerZjC980raeT1rbjAMz/Jow7+EkY68YwEJtkGDMQClzj2rev q1y7g8uok0yRQ== Date: Thu, 30 May 2019 13:17:21 +1000 From: Stephen Rothwell To: "Eric W. Biederman" , Vineet Gupta Cc: Linux Next Mailing List , Linux Kernel Mailing List , Eugeniy Paltsev Subject: linux-next: manual merge of the userns tree with the arc-current tree Message-ID: <20190530131721.0af603a4@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/w7Q+15IzRn7eThtdIF/Em2R"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/w7Q+15IzRn7eThtdIF/Em2R Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi all, Today's linux-next merge of the userns tree got a conflict in: arch/arc/mm/fault.c between commits: a8c715b4dd73 ("ARC: mm: SIGSEGV userspace trying to access kernel virtual= memory") ea3885229b0f ("ARC: mm: do_page_fault refactor #5: scoot no_context to en= d") acc639eca380 ("ARC: mm: do_page_fault refactor #6: error handlers to use = same pattern") 0c85612550a4 ("ARC: mm: do_page_fault refactor #7: fold the various error= handling") c5d7f7610d88 ("ARC: mm: do_page_fault refactor #8: release mmap_sem soone= r") from the arc-current tree and commits: 351b6825b3a9 ("signal: Explicitly call force_sig_fault on current") 2e1661d26736 ("signal: Remove the task parameter from force_sig_fault") from the userns tree. I fixed it up (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. --=20 Cheers, Stephen Rothwell diff --cc arch/arc/mm/fault.c index e93ea06c214c,5001f6418e92..000000000000 --- a/arch/arc/mm/fault.c +++ b/arch/arc/mm/fault.c @@@ -187,21 -228,14 +187,21 @@@ bad_area return; } =20 - goto no_context; + if (fault & VM_FAULT_SIGBUS) { + sig =3D SIGBUS; + si_code =3D BUS_ADRERR; + } + else { + sig =3D SIGSEGV; + } =20 -do_sigbus: - up_read(&mm->mmap_sem); + tsk->thread.fault_address =3D address; - force_sig_fault(sig, si_code, (void __user *)address, tsk); ++ force_sig_fault(sig, si_code, (void __user *)address); + return; =20 - if (!user_mode(regs)) - goto no_context; +no_context: + if (fixup_exception(regs)) + return; =20 - tsk->thread.fault_address =3D address; - force_sig_fault(SIGBUS, BUS_ADRERR, (void __user *)address); + die("Oops", regs, address); } --Sig_/w7Q+15IzRn7eThtdIF/Em2R Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAlzvS0EACgkQAVBC80lX 0GxwLgf/Yb+XKEDiDHSEM4zEm0mSb5MepeW7+pG1D15FoMHOPIiG92B4sRcKtXSL P7MMxkKxKNOM95FcHmu26wn6E4LsHGxSPx8L9R3mNfcWxfeLxysNY6EHWuFpAzHe yqJhRimVsms/kNkj5+TJYYBz4dYMcapMfA7jvpZOaHOW2aaM9Ptkptm8CAW7C0jh NyE1tCTrGCoudV1rFrOz2W7JiW5qLe4+MgLuUZev+M+feyBgWZZCxWDGNx3HSFOr l9a5Pg9B9+PFbct3RV7HEH3k+7rFnqlYgmD41dB1CkKmZ/iEUuSpTYdSoNoCAWB/ IcWjfJmSMRS40RUndj2UAYT9sqViGw== =zGZo -----END PGP SIGNATURE----- --Sig_/w7Q+15IzRn7eThtdIF/Em2R--