From: Wang Yugui <wangyugui@e16-tech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, hch@lst.de
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
Subject: Re: [PATCH 6.1 000/183] 6.1.7-rc1 review
Date: Wed, 18 Jan 2023 10:14:35 +0800 [thread overview]
Message-ID: <20230118101433.734D.409509F4@e16-tech.com> (raw)
In-Reply-To: <Y8Znr6CAFi8ikhdH@kroah.com>
Hi,
> On Tue, Jan 17, 2023 at 03:11:37PM +0800, Wang Yugui wrote:
> > Hi,
> >
> > fstests(generic/034, xfs) panic when 6.1.7-rc1, but not panic when 6.1.6.
> >
> > It seems patch *1 related.
> > *1 Subject: blk-mq: move the srcu_struct used for quiescing to the tagset
> > From: Christoph Hellwig <hch@lst.de>
> >
> > This patch has been drop from 6.1.2-rc1. and it now added in 6.1.7-rc1 again.
> >
> > the panic in 6.1.7-rc1 is almost same as that in 6.1.2-rc1.
>
> Argh, yes, let me go drop these again.
>
> Sasha, can you blacklist these from your tools so they don't get picked
> up again?
this panic does not happen on upstream 6.2.0-rc4.
or maybe we need a bigger patch set?
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/01/18
next prev parent reply other threads:[~2023-01-18 2:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 15:48 [PATCH 6.1 000/183] 6.1.7-rc1 review Greg Kroah-Hartman
2023-01-16 22:38 ` Conor Dooley
2023-01-16 23:55 ` Shuah Khan
2023-01-17 2:05 ` Justin Forbes
2023-01-17 4:14 ` ogasawara takeshi
2023-01-17 7:11 ` Wang Yugui
2023-01-17 9:17 ` Greg Kroah-Hartman
2023-01-18 2:14 ` Wang Yugui [this message]
2023-01-18 6:08 ` Greg Kroah-Hartman
2023-01-17 8:40 ` Rudi Heitbaum
2023-01-17 9:01 ` Bagas Sanjaya
2023-01-17 9:32 ` Ron Economos
2023-01-17 10:05 ` Naresh Kamboju
2023-01-17 12:18 ` Jon Hunter
2023-01-17 12:43 ` Sudip Mukherjee
2023-01-17 13:21 ` Allen Pais
-- strict thread matches above, loose matches on Subject: below --
2023-01-16 20:58 Ronald Warsow
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=20230118101433.734D.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jonathanh@nvidia.com \
--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=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 \
/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