Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4646290imm; Mon, 14 May 2018 10:29:02 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoeEgJohyG6h1AqIFr3SfFp2bAIn/0zS2R7N0ZD/6qRBuDCenSNgJ8Z6NODtLyJxL3y/tUg X-Received: by 2002:a62:4353:: with SMTP id q80-v6mr11479169pfa.228.1526318942851; Mon, 14 May 2018 10:29:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526318942; cv=none; d=google.com; s=arc-20160816; b=C0iQ81d5Wyz/IDbHxFCaWFutsdSV8cvi9Mqo3Xwzh+EQ1HKuAGQeoYJNq2GkyBYz94 GSEEEh+/Ulbrwf9a0SEgbi+idKToLTKsKeYGTymj+hULQfgWtXip9XIwQ0zDw/IIxk0X in9uf2G8QRQzhwgvDvgF4RHeOpaRG+mmUalGuVxLf+Lws7Z0Sl9dPMcGiTSDWTnp1F7d mfHOXh4ALKF2THsBUEucvH0sCOGlCzdMBDFyXY3lPoj4WiTZqZISkJiRRZzSr1ATl59L UuXVVZF84rHf5PaQM4FjCnifT7onPvHdVnr5Jn6bfI7/u0I5hxl90n3HZZ/dorO4COGy 4Vpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=LxpCfTw2AEMMUM0aBzzfXXb0awN5GsuLbM5+YV+OZPU=; b=cO/taHjFZh/lSFJq3Rzbj069iIgmJwfpJ3HkiwgUFb60A8oRIDCrcA+BTOvrxykWYU eQP6pHn7TlobT1Hw4cBwm0wqRhheFHMYAzN0DalZ47aOwAtTbCZef92W9QEitjNrvYH+ LvzaBA7Wm/K6fHcgUenfFPDc1fFhRV8Wq69J16/IvBSgi7PhXHgkuLV1giTJBCkJDKOa 1xqZMlbMz3xD6QEMu+Wd51dw8EvY6TMuZgGQE1SZfNFhEpHvPoAsckAVZyuo5dvEE3Lj t1/g4C0f6DjBXXXkR4PIzJFyuv9T1ayRUkSJyDON0pog0ghpykFfbgqNKLStj5lbdyi/ 1XIw== ARC-Authentication-Results: i=1; mx.google.com; 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 u6-v6si686318pgb.648.2018.05.14.10.28.48; Mon, 14 May 2018 10:29:02 -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; 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 S1755192AbeENQfL (ORCPT + 99 others); Mon, 14 May 2018 12:35:11 -0400 Received: from mx2.suse.de ([195.135.220.15]:41255 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752691AbeENQfJ (ORCPT ); Mon, 14 May 2018 12:35:09 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 70500AE89; Mon, 14 May 2018 16:35:08 +0000 (UTC) Date: Mon, 14 May 2018 09:19:10 -0700 From: Davidlohr Bueso To: Vlastimil Babka Cc: akpm@linux-foundation.org, aarcange@redhat.com, joe.lawrence@redhat.com, gareth.evans@contextis.co.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org, stable@kernel.org, ltp@lists.linux.it Subject: Re: [PATCH -next 0/2] ipc/shm: shmat() fixes around nil-page Message-ID: <20180514161910.gbt32tfsocpddaav@linux-n805> Mail-Followup-To: Vlastimil Babka , akpm@linux-foundation.org, aarcange@redhat.com, joe.lawrence@redhat.com, gareth.evans@contextis.co.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org, stable@kernel.org, ltp@lists.linux.it References: <20180503203243.15045-1-dave@stgolabs.net> <8addf0c1-26cd-add9-fb9c-292cc3567014@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <8addf0c1-26cd-add9-fb9c-292cc3567014@suse.cz> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 10 May 2018, Vlastimil Babka wrote: >Can you add appropriate Fixes: tags if possible? I guess patch 1 is >clear, dunno about patch 2... Right, patch 1 would still benefit from Fixes tag. As to patch 2, the bug as been there since forever (pre-dates git history). But yeah, as both come together and are related to a certain extent, the same Fixes could serve both patches. Thanks, Davidlohr