From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="EbVOsNIx" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F27610F for ; Sun, 26 Nov 2023 15:44:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701042269; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eXjCU1JMw8WXLHo5e8MuCVi+8FCFwFKjN2ELDKbyjzQ=; b=EbVOsNIxAILOjVi6KLmVwqc3YoYKVzbDcqHvz/cilLQinfAofkcd7kw7d/F3/AKupKHvQp 1P7LMNHr4nu3if3csBmkCGksHgxafStsUhxyqpMla7qo4+bYXpSxyZT/7PyWcTXpZ00GK0 oHIOfGmvgEplYwzNOZxIsKtsE+6mmHI= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-657-LqD3yBzGPx2fdXQpWo1BRw-1; Sun, 26 Nov 2023 18:44:27 -0500 X-MC-Unique: LqD3yBzGPx2fdXQpWo1BRw-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 43A2938062A5; Sun, 26 Nov 2023 23:44:27 +0000 (UTC) Received: from localhost (unknown [10.22.16.162]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5770A492BE7; Sun, 26 Nov 2023 23:44:26 +0000 (UTC) Date: Sun, 26 Nov 2023 20:44:25 -0300 From: "Luis Claudio R. Goncalves" To: Greg Kroah-Hartman Cc: LKML , linux-rt-users , stable-rt , Steven Rostedt , Thomas Gleixner , Carsten Emde , Sebastian Andrzej Siewior , Daniel Wagner , Tom Zanussi , Clark Williams , Mark Gross , Pavel Machek , Jeff Brady Subject: Re: [ANNOUNCE] 5.10.201-rt98 Message-ID: References: <2023112455-anytime-unmapped-ed7d@gregkh> Precedence: bulk X-Mailing-List: linux-rt-users@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2023112455-anytime-unmapped-ed7d@gregkh> X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9 On Fri, Nov 24, 2023 at 04:11:35PM +0000, Greg Kroah-Hartman wrote: > On Wed, Nov 22, 2023 at 10:36:23AM -0300, Luis Claudio R. Goncalves wrote: > > On Tue, Nov 21, 2023 at 10:01:25PM -0300, Luis Claudio R. Goncalves wrote: > > > Hello RT-list! > > > > > > I'm pleased to announce the 5.10.201-rt98 stable release. > > > > > > This release is just an update to the new stable 5.10.201 > > > version and no RT changes have been made. > > > > > > You can get this release via the git tree at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git > > > > > > branch: v5.10-rt > > > Head SHA1: 3a93f0a0d49dd0db4c6876ca9a7369350e64320e > > > > Greg KH, > > > > While testing v5.10.201-rt98 I stumbled over this warning: > > > > [ 1000.312397] run blktests nvme/005 at 2023-11-21 21:46:30 > > ... > > [ 1000.500478] workqueue: WQ_MEM_RECLAIM nvmet_tcp_wq:nvmet_tcp_io_work [nvmet_tcp] is flushing !WQ_MEM_RECLAIM events:0x0 > > [ 1000.500490] WARNING: CPU: 0 PID: 6 at kernel/workqueue.c:2620 check_flush_dependency+0x11f/0x140 > > > > That seems to be fixed by: > > > > 533d2e8b4d5e4 nvmet-tcp: fix lockdep complaint on nvmet_tcp_wq flush during queue teardown > > (and depending on what else is backported) > > ddd2b8de9f85b nvmet: fix workqueue MEM_RECLAIM flushing dependency > > > > Is this something that can be added to your v5.10 queue or should I carry > > this fix on v5.10-rt in the meantime? > > That's odd, as this commit is already in the 5.10.138 release, so how > can we apply it again? I am really sorry for the confusion on my side. Either myself of the CI I used mixed up the test branches and ended up using older code. And I missed that when reviewing the results. > confused, Sorry again. I owe you a (root?) beer next LPC. > greg k-h Best regards, Luis