From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A166AC31E49 for ; Thu, 13 Jun 2019 15:48:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 71A8620B7C for ; Thu, 13 Jun 2019 15:48:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560440933; bh=YHsBlYY6tsrVcysOLrS4tUMHlZFvYKYdWz8QfYHbYF0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=IB2Q3RAocdzhlhlHKpBcD/4w9/MpG8n3FWrvSIdSmtwWmVSsT+X/L43ApvRmRWgHU V9ZD3hmK7S9cITjqCavkxoyiq+apV/g0yyWNbAuJqJZYti+Z7AV7khzYzB1ehGGpsm I4XN22EATfxGdo2AS5cVgvkgxxZ79J1esiuVKQow= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389236AbfFMPsw (ORCPT ); Thu, 13 Jun 2019 11:48:52 -0400 Received: from mail.kernel.org ([198.145.29.99]:45638 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731709AbfFMJOd (ORCPT ); Thu, 13 Jun 2019 05:14:33 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6EF0D2133D; Thu, 13 Jun 2019 09:14:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1560417272; bh=YHsBlYY6tsrVcysOLrS4tUMHlZFvYKYdWz8QfYHbYF0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=aWKMs2qselRXwjVuccRgFuwYdWSJG9elv1+wDvNoy3snAq8CN1VPvkgRhEyAHNx7R /grEVBUAKWwzzK+buGMkQHcXsHuJriEn2gbOqTolAQKs/XCDEF4K11idIYljbvfHnp T9sRFlavEToI0bbB0gO8Ddn2fWDn1ExlbSmjQcEA= Date: Thu, 13 Jun 2019 11:14:30 +0200 From: Greg Kroah-Hartman To: Jens Axboe Cc: Stephen Bates , Mark Rutland , "linux-block@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "shhuiw@foxmail.com" , Logan Gunthorpe , "viro@zeniv.linux.org.uk" Subject: Re: [PATCH] io_uring: fix SQPOLL cpu check Message-ID: <20190613091430.GA28704@kroah.com> References: <5D2859FE-DB39-48F5-BBB5-6EDD3791B6C3@raithlin.com> <20190612092403.GA38578@lakrids.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, Jun 13, 2019 at 02:54:45AM -0600, Jens Axboe wrote: > On 6/12/19 3:47 AM, Stephen Bates wrote: > >> Aargh. My original patch [1] handled that correctly, and this case was > >> explicitly called out in the commit message, which was retained even > >> when the patch was "simplified". That's rather disappointing. :/ > > > > It looks like Jens did a fix for this (44a9bd18a0f06bba > > " io_uring: fix failure to verify SQ_AFF cpu") which is in the 5.2-rc series > > but which hasn’t been applied to the stable series yet. I am not sure how > > I missed that but it makes my patch redundant. > > > > Jens, will 44a9bd18a0f06bba be applied to stable kernels? > > Yes, we can get it flagged for stable. Greg, can you pull in the above > commit for 5.1 stable? Now snuck in for the next 5.1.y release, thanks. greg k-h