On Thu, Jul 10, 2025 at 06:18:39PM +0800, Wenli Quan wrote:
> On Wed, Jul 9, 2025 at 9:08 PM Dragos Tatulea <[email protected]> wrote:
> >
> > On Wed, Jul 09, 2025 at 08:59:13PM +0800, Wenli Quan wrote:
> > > On Wed, Jul 9, 2025 at 6:38 PM Dragos Tatulea <[email protected]> wrote:
> > > >
> > > > On Wed, Jul 09, 2025 at 05:36:04PM +0800, Wenli Quan wrote:
> > > > > I am reporting an issue where the host system crashes when re-running
> > > > > a script that creates a vDPA device after interrupting its previous
> > > > > execution. I am attaching the script for your analysis, as I am unsure
> > > > > of the exact step causing the crash.
> > > > >
> > > > Thanks for catching this Wenli. We'll look into it.
> > > >
> > > > > # uname -r
> > > > > 6.16.0-rc2
> > > > > # sh vdpa-setup.sh 0000:b5:00.1 1
> > > > > interrupted by pressing Ctrl+C
> > > > Could you specify during which stage of the script do you interrupt it?
> > >
> > > Interrupted after running for a few seconds.
> > >
> > I was not yet able to reproduce the issue.
> >
> > Could you print out the commands of the debug script so that we can see
> > where it was interrupted? set -x should be enough.
>
> I tried again many times, just to reproduce once. the following script
> for your inference. but it doesn’t cause a crash every time.
>
Hi Wenli,
Could you try re-running this again please with the latest mainline as I
was not able to reproduce it.
There was a relevant fix [0] recently that might make a difference.
This was merged as commit
6b4be64fd9fe ("net/mlx5e: Harden uplink netdev access against device unbind")
in mainline.
[0]
https://lore.kernel.org/all/[email protected]/
Thanks,
Dragos
