[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220315074834-mutt-send-email-mst@kernel.org>
Date: Tue, 15 Mar 2022 07:50:10 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Anirudh Rayabharam <mail@...rudhrb.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
syzbot+0abd373e2e50d704db87@...kaller.appspotmail.com,
Sasha Levin <sashal@...nel.org>, jasowang@...hat.com
Subject: Re: [PATCH 5.15 015/110] vhost: fix hung thread due to erroneous
iotlb entries
On Tue, Mar 15, 2022 at 10:19:52AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Mar 14, 2022 at 09:44:43PM +0530, Anirudh Rayabharam wrote:
> > Mon, Mar 14, 2022 at 12:53:17PM +0100, Greg Kroah-Hartman wrote:
> > > From: Anirudh Rayabharam <mail@...rudhrb.com>
> > >
> > > [ Upstream commit e2ae38cf3d91837a493cb2093c87700ff3cbe667 ]
> >
> > This breaks batching of IOTLB messages. [1] fixes it but hasn't landed in
> > Linus' tree yet.
> >
> > [1]: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git/commit/?h=linux-next&id=95932ab2ea07b79cdb33121e2f40ccda9e6a73b5
>
> Why is this tree not in linux-next? I don't see this commit there, so
> how can it get to Linus properly?
>
> thanks,
>
> greg k-h
It is in next normally. I was sure this commit was there too. I'm not sure
what happened, maybe I forgot to push :(
Powered by blists - more mailing lists