Linux-HyperV List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kelsey Steele <kelseysteele@linux.microsoft.com>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	decui@microsoft.com, petrtesarik@huaweicloud.com,
	linux-hyperv@vger.kernel.org, iommu@lists.linux.dev,
	robin.murphy@arm.com, dexuan.linux@gmail.com,
	tyler.hicks@microsoft.com
Subject: Re: [PATCH 6.1 000/179] 6.1.23-rc2 review
Date: Wed, 5 Apr 2023 11:30:25 +0200	[thread overview]
Message-ID: <2023040503-perkiness-nutty-f8f4@gregkh> (raw)
In-Reply-To: <20230405003549.GA21326@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>

On Tue, Apr 04, 2023 at 05:35:49PM -0700, Kelsey Steele wrote:
> On Tue, Apr 04, 2023 at 08:32:15PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.23 release.
> > There are 179 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Thu, 06 Apr 2023 18:31:13 +0000.
> > Anything received after that time might be too late.
> > 
> 
> Hi Greg, 
> 
> 6.1.23-rc2 is failing to boot on x86 WSL. A bisect leads to commit
> c2f05366b687 ("swiotlb: fix slot alignment checks") being the problem
> and reverting this patch puts everything back in a working state.
> 
> There's a report from Dexuan who also encountered this error on a Linux
> VM on Hyper-V:
> 
> https://lore.kernel.org/all/CAA42JLa1y9jJ7BgQvXeUYQh-K2mDNHd2BYZ4iZUz33r5zY7oAQ@mail.gmail.com/
> 
> Adding a chunk of my log below which shows errors occuring from the hv_strvsc driver.

Is this also a problem on 6.2-rc1, and Linus's tree?

thanks,

greg k-h

  reply	other threads:[~2023-04-05  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230404183150.381314754@linuxfoundation.org>
2023-04-05  0:35 ` [PATCH 6.1 000/179] 6.1.23-rc2 review Kelsey Steele
2023-04-05  9:30   ` Greg Kroah-Hartman [this message]
2023-04-05  9:41     ` Petr Tesarik
2023-04-05  9:46       ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2023040503-perkiness-nutty-f8f4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=decui@microsoft.com \
    --cc=dexuan.linux@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=iommu@lists.linux.dev \
    --cc=jonathanh@nvidia.com \
    --cc=kelseysteele@linux.microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=petrtesarik@huaweicloud.com \
    --cc=robin.murphy@arm.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tyler.hicks@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox