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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 571E8C46467 for ; Mon, 16 Jan 2023 15:44:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230331AbjAPPoo (ORCPT ); Mon, 16 Jan 2023 10:44:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60698 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231171AbjAPPol (ORCPT ); Mon, 16 Jan 2023 10:44:41 -0500 Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94EAE1E289 for ; Mon, 16 Jan 2023 07:44:39 -0800 (PST) Received: by mail-pj1-x102d.google.com with SMTP id m7-20020a17090a730700b00225ebb9cd01so34237421pjk.3 for ; Mon, 16 Jan 2023 07:44:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=ep+gu8Wzxz1XzGkyuWB0bLCmC8cV8aaLkxDrtlaBNIE=; b=c9zNawnK2UWJhD/sNZEYHGKiNRlWVDyJijBtFtC8agG3fvskxGdpuCfktsi/Lotk9X pIx7QRICwargwIAnL5DuRxsUS0SIYEuq1t07E1RKcyacojSWF3KkzwrFGAyqlMOiV1IE s7OkG9vlFc4Al7DdkOWL+V9RVs/rhEMiNvWZRTy8vZgKc/ZCZK3++xFtE6u4c83mtXN8 hftxLgO3Rv1kD2AcwM7y82t3Oh+0u+dKixBRpiwSgDAjNKF2Z3lwGPeWVXj4ZpehAVnm HYIj23INl6+EAGxC3EeAiGIAaNeYB+lhXaKlP48JC0WPEhaOv03T7bmgUjR9MAPctPuA t5DA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ep+gu8Wzxz1XzGkyuWB0bLCmC8cV8aaLkxDrtlaBNIE=; b=N8Yi8XTAuY7bs+0lAbbskadgvbDHEsJfJgvAkpomjPT7pMa1kKttqnyTkjfNGk/fBC Xt449vkyHMkUo0carN/umWLJE46iqA6fW07+a/XuCJB9U2tL0uJZ+M32jC4nXoSXlgkl 5gD98lF7egdB55OUAhPWXpE2dTSYGu225Zd6smmD9JHNVSl787D/314bRwcq54XWv7YZ 6i/8CkKlD/TBpKXxXaWnkLTWN6Z5LYm16BfV4dmCbVJOck1CwqnaDdQ7N4GQi542LDNG LBxUA7oS1wMmuVFQNNOowKqhNhcLq9ZXz8sApwawGywkFjjlTEmhsVRhINVeFl/S3ST3 vDTQ== X-Gm-Message-State: AFqh2kr2es3jScuKLb3fEI8I3WIvTeb46m/vtXFmOevOJIKerskpRkpd udmkdrGgLS5HXczQgW/EvavWZA== X-Google-Smtp-Source: AMrXdXt0BZIJaIf2dPN5YJX2ElhkSG66V59emcBOnQUbzsek5vKyKYZiPt7whP8yZXNyuRHMVUbr5Q== X-Received: by 2002:a17:902:d3c9:b0:189:b74f:46ad with SMTP id w9-20020a170902d3c900b00189b74f46admr53348plb.3.1673883879034; Mon, 16 Jan 2023 07:44:39 -0800 (PST) Received: from [192.168.1.136] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id e3-20020a17090301c300b00172cb8b97a8sm5715112plh.5.2023.01.16.07.44.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 16 Jan 2023 07:44:38 -0800 (PST) Message-ID: Date: Mon, 16 Jan 2023 08:44:37 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: =?UTF-8?Q?Re=3a_=5bregression=5d_Bug=c2=a0216932_-_io=5furing_with_?= =?UTF-8?Q?libvirt_cause_kernel_NULL_pointer_dereference_since_6=2e1=2e5?= Content-Language: en-US To: Greg Kroah-Hartman Cc: Linux regressions mailing list , "stable@vger.kernel.org" , io-uring@vger.kernel.org, LKML , "Sergey V." References: <74347fe1-ac68-2661-500d-b87fab6994f7@leemhuis.info> From: Jens Axboe In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On 1/16/23 7:49 AM, Greg Kroah-Hartman wrote: > On Mon, Jan 16, 2023 at 07:13:40AM -0700, Jens Axboe wrote: >> On 1/16/23 6:42 AM, Jens Axboe wrote: >>> On 1/16/23 6:17?AM, Linux kernel regression tracking (Thorsten Leemhuis) wrote: >>>> Hi, this is your Linux kernel regression tracker. >>>> >>>> I noticed a regression report in bugzilla.kernel.org. As many (most?) >>>> kernel developer don't keep an eye on it, I decided to forward it by >>>> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216932 : >>> >>> Looks like: >>> >>> commit 6d47e0f6a535701134d950db65eb8fe1edf0b575 >>> Author: Jens Axboe >>> Date: Wed Jan 4 08:52:06 2023 -0700 >>> >>> block: don't allow splitting of a REQ_NOWAIT bio >>> >>> got picked up by stable, but not the required prep patch: >>> >>> >>> commit 613b14884b8595e20b9fac4126bf627313827fbe >>> Author: Jens Axboe >>> Date: Wed Jan 4 08:51:19 2023 -0700 >>> >>> block: handle bio_split_to_limits() NULL return >>> >>> Greg/team, can you pick the latter too? It'll pick cleanly for >>> 6.1-stable, not sure how far back the other patch has gone yet. >> >> Looked back, and 5.15 has it too, but the cherry-pick won't work >> on that kernel. >> >> Here's one for 5.15-stable that I verified crashes before this one, >> and works with it. Haven't done an allmodconfig yet... > > All now queued up, thanks! Thanks Greg! This one was my fault, as it was a set of 2 patches and I only marked 2/2 for stable. But how is that best handled? 1/2 could've been marked stable as well, but I don't think that would have prevented 2/2 applying fine and 1/2 failing and hence not getting queued up until I would've done a backport. What's the recommended way to describe the dependency that you only want 2/2 applied when 1/2 is in as well? -- Jens Axboe