From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 102F9320F for ; Tue, 14 May 2024 12:11:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715688665; cv=none; b=WxKDGEajq/qrKGlOqBsUXCGVQWC6CIF3Dhq9y9RSqAskFwN6a87r6DDuZqXrLga0HG1+FZAEgMMmdaGp0JEKxR+jyTfAOCQ68yj2xVnAasPjmQS73E9qtzr/VXo83WMkSjiic5Cn9/6rUpisYl4ps2WyBb73cSNt8KeKQ01/DNg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715688665; c=relaxed/simple; bh=8EwPf+ZMZBkhQ2eD1+QAwSn0u+dsVHe+C2d0clf1Wn8=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=RDcTdQ8ODDkgtAFiLVYvQ7C+FbaMf8bPFmECFkHRdqA2TJRTMKD8KvxgIuyZgcxWF7OivqbjpKc/HfTVeZN0cnacvi9y4TSRancReNSVXOTOTL3nySWBXkaiq8XjWr8SCHID6GNe+4l1NYNYfe2g27rUrRb3s0Z2Nnn2UhiLnhQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=HEYCZueX; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="HEYCZueX" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3865EC2BD10; Tue, 14 May 2024 12:11:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1715688664; bh=8EwPf+ZMZBkhQ2eD1+QAwSn0u+dsVHe+C2d0clf1Wn8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HEYCZueXLZIu8TfKcoqmirrG4IP7SKIS+UchidNdUQ5omNfTLtRXNWQ/lC+08sDVB /AYOFfmj/NaM2fgpMqnxuhmZKUTYZGi9olfz7GZGqB+zYTQiMUEGcV65aTbcJMyPT6 qUPDJw2X1opOoZqptVtujtWsbfcDw2wKG+gjJJpA= Date: Tue, 14 May 2024 14:11:01 +0200 From: Greg KH To: Ronnie Sahlberg Cc: stable@vger.kernel.org Subject: Re: commits for stable 2024-05-11 Message-ID: <2024051443-chant-duffel-8529@gregkh> References: <2024051256-joyfully-unframed-dd66@gregkh> Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Sun, May 12, 2024 at 06:35:05PM -0400, Ronnie Sahlberg wrote: > On Sun, May 12, 2024 at 8:21 AM Greg KH wrote: > > > > On Sat, May 11, 2024 at 09:13:25PM -0400, Ronnie Sahlberg wrote: > > > Please find attached a report generated by keyword matching commits > > > from upstream that may be suitable for stable and probably as CVEs as > > > well. > > > > This is great, thanks for looking into this and sending this out! > > > > > I exclude commits that are already tagged with CC stable in upstream > > > and also commits already in > > > stable/linux-rolling-stable. > > > > I took a very short look, and just picked one commit at random on the > > bottom of the list: > > cf2df0080bd59cb97a15 > > > > And it's included in 6.8.2 already, as commit `0 ("wifi: > > ath11k: fix a possible dead lock caused by ab->base_lock"). > > > > So is your tooling working? > > Thankyou. > Ah, the marking of which upstream commit that stable uses is not consistent. > That one (and another ~150) used the form : > "^ [ Upstream commit cf2df0080bd59cb97a1519ddefaf59788febdaa5 ]" > and my regex did not accept that. > I have changed the regex to be more permissive in detecting what is a > reference to an upstream commit > and it should be detecting this varient correctly now. > > > > > > Also, give us a chance to catch up on commits that are in Linus's tree, > > but not in a -rc release, which you list a few at the top of the list. > > We aren't allowed to apply them until after they hit a -rc release. > > I see. > So we should not backporting anything more recent than the most recent > tag in upstream master? > Ok. I have done that change to fix that. > > Please find attached a new version of the report. > I also change the format slightly on how the commits are listed so > that it IMO becomes easier to read > and check for specific types of hits. > > I have attached an updated scan with > 1, fix for being more tolerant when detecting commit references > 2, stops scanning at the most recent tag in upstream master > > Once this format of the report is in a good shape and we sort out all > the bugs in it > I can set it up to scan and automatically post to the list once a week or so. Thanks, I'll look at this later this week after this latest round of -rc releases are out. greg k-h