netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Shinas Rasheed <srasheed@marvell.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: hgani@marvell.com, sedara@marvell.com, vimleshk@marvell.com,
	thaller@redhat.com, wizhao@redhat.com, kheib@redhat.com,
	egallen@redhat.com, konguyen@redhat.com, horms@kernel.org,
	frank.feng@synaxg.com, Veerasenareddy Burru <vburru@marvell.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Abhijit Ayarekar <aayarekar@marvell.com>,
	Satananda Burla <sburla@marvell.com>
Subject: Re: [PATCH net v3 1/7] octeon_ep: Add checks to fix double free crashes.
Date: Sat, 9 Nov 2024 15:10:54 +0000	[thread overview]
Message-ID: <bdaa8da4-aa72-43de-8b05-88ed52573a8a@linux.dev> (raw)
In-Reply-To: <20241108074543.1123036-2-srasheed@marvell.com>

On 08/11/2024 07:45, Shinas Rasheed wrote:
> From: Vimlesh Kumar <vimleshk@marvell.com>
> 
> Add required checks to avoid double free. Crashes were
> observed due to the same on reset scenarios
> 
> Fixes: 37d79d059606 ("octeon_ep: add Tx/Rx processing and interrupt support")
> Signed-off-by: Vimlesh Kumar <vimleshk@marvell.com>
> Signed-off-by: Shinas Rasheed <srasheed@marvell.com>

As you reposted in <24h, could you please take a look at the comments in v2?

FYI, 24h rule in netdev:
https://docs.kernel.org/process/maintainer-netdev.html

Thanks.

  reply	other threads:[~2024-11-09 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  7:45 [PATCH net v3 0/7] Double free fixes and NULL pointer checks Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 1/7] octeon_ep: Add checks to fix double free crashes Shinas Rasheed
2024-11-09 15:10   ` Vadim Fedorenko [this message]
2024-11-11  5:21     ` [EXTERNAL] " Shinas Rasheed
2024-11-12 13:03       ` Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 2/7] octeon_ep: Fix null dereferences to IQ/OQ pointers Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 3/7] octeon_ep: add protective null checks in napi callbacks for cn9k cards Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 4/7] octeon_ep: add protective null checks in napi callbacks for cnxk cards Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 5/7] octeon_ep_vf: Fix null dereferences to IQ/OQ pointers Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 6/7] octeon_ep_vf: add protective null checks in napi callbacks for cn9k cards Shinas Rasheed
2024-11-08  7:45 ` [PATCH net v3 7/7] octeon_ep_vf: add protective null checks in napi callbacks for cnxk cards Shinas Rasheed

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=bdaa8da4-aa72-43de-8b05-88ed52573a8a@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=aayarekar@marvell.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=egallen@redhat.com \
    --cc=frank.feng@synaxg.com \
    --cc=hgani@marvell.com \
    --cc=horms@kernel.org \
    --cc=kheib@redhat.com \
    --cc=konguyen@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sburla@marvell.com \
    --cc=sedara@marvell.com \
    --cc=srasheed@marvell.com \
    --cc=thaller@redhat.com \
    --cc=vburru@marvell.com \
    --cc=vimleshk@marvell.com \
    --cc=wizhao@redhat.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;
as well as URLs for NNTP newsgroup(s).