lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <CO1PR18MB47473C9867B184DDDB51E1C5D817A@CO1PR18MB4747.namprd18.prod.outlook.com>
Date: Wed, 17 Sep 2025 12:24:22 +0000
From: Sathesh B Edara <sedara@...vell.com>
To: Simon Horman <horms@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Satananda
 Burla <sburla@...vell.com>,
        Veerasenareddy Burru <vburru@...vell.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "edumazet@...gle.com"
	<edumazet@...gle.com>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>,
        Haseeb Gani <hgani@...vell.com>, "andrew@...n.ch"
	<andrew@...n.ch>,
        Shinas Rasheed <srasheed@...vell.com>
Subject: RE: [EXTERNAL] Re: [net PATCH v2] octeon_ep: Clear VF info at PF when
 VF driver is removed


> On Tue, Sep 16, 2025 at 06:12:25AM -0700, Sathesh B Edara wrote:
> > When a VF (Virtual Function) driver is removed, the PF (Physical
> > Function) driver continues to retain stale VF-specific information.
> > This can lead to inconsistencies or unexpected behavior when the VF is
> > re-initialized or reassigned.
> >
> > This patch ensures that the PF driver clears the corresponding VF info
> > when the VF driver is removed, maintaining a clean state and
> > preventing potential issues.
> >
> > Fixes: cde29af9e68e ("octeon_ep: add PF-VF mailbox communication")
> > Signed-off-by: Sathesh B Edara <sedara@...vell.com>
> > ---
> > Changes:
> > V2:
> >   - Commit header format corrected.
> 
> Hi,
> 
> I feel that I must be missing something terribly obvious.
> But this patch seems to be a subset of the one at the link below.
> 
You're absolutely right — apologies for the confusion. I mistakenly sent the wrong patch and so marked its state as 'Not Applicable'.
 Please disregard this patch.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ