From: Wang Yugui <wangyugui@e16-tech.com>
To: Shay Drori <shayd@nvidia.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>, <akpm@linux-foundation.org>,
<torvalds@linux-foundation.org>, <stable@vger.kernel.org>,
<lwn@lwn.net>, <jslaby@suse.cz>
Subject: Re: Linux 6.6.28
Date: Sun, 21 Apr 2024 07:00:26 +0800 [thread overview]
Message-ID: <20240421070025.C32F.409509F4@e16-tech.com> (raw)
In-Reply-To: <220e55df-a0a2-4272-b94f-c7c4c6fbf2b7@nvidia.com>
Hi,
>
>
> On 20/04/2024 8:59, Wang Yugui wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > Hi,
> >
> >> I'm announcing the release of the 6.6.28 kernel.
> >>
> >> All users of the 6.6 kernel series must upgrade.
> >>
> >> The updated 6.6.y git tree can be found at:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.6.y
> >> and can be browsed at the normal kernel.org git web browser:
> >> https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> >
> > Linux 6.6.28 failed to boot with the following panic *1 on a server with
> > mellonax CX-6 VPI NIC, but 6.6.27/6.1.87 boot well.
> >
> > After reverting 'net/mlx5: Restore mistakenly dropped parts in register devlink
> > flow', linux boot well.
> >
> there is a similar discussion in net-dev ML[1].
> In short, it seems this patch is missing from stable, which is prerequisite for the bad patch:
> 0553e753ea9e
> "net/mlx5: E-switch, store eswitch pointer before registering devlink_param".
>
> Wang, can you test it out please?
After apply "net/mlx5: E-switch, store eswitch pointer before registering devlink_param"
to 6.6.28, linux boot well here.
and "net/mlx5: Restore mistakenly dropped parts in register devlink flow" is
NOT applied here.
Thanks a lot.
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2024/04/21
prev parent reply other threads:[~2024-04-20 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 9:34 Linux 6.6.28 Greg Kroah-Hartman
2024-04-17 9:34 ` Greg Kroah-Hartman
2024-04-20 5:59 ` Wang Yugui
2024-04-20 18:28 ` Shay Drori
2024-04-20 23:00 ` Wang Yugui [this message]
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=20240421070025.C32F.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=shayd@nvidia.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.