netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Matthias Stocker <mstocker@barracuda.com>
Cc: "pv-drivers@vmware.com" <pv-drivers@vmware.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"doshir@vmware.com" <doshir@vmware.com>
Subject: Re: [PATCH] vmxnet3: disable rx data ring on dma allocation failure
Date: Thu, 30 May 2024 15:17:49 -0700	[thread overview]
Message-ID: <20240530151749.7118e4da@kernel.org> (raw)
In-Reply-To: <f3cee80744acbad74fed1b653f2b3bd32856bfb0.camel@barracuda.com>

On Thu, 30 May 2024 16:00:22 +0000 Matthias Stocker wrote:
> Whereas when I reverted the above mentioned commit 6f4833383e85 ("net:
> vmxnet3: Fix NULL pointer dereference and applied the patch I've
> submitted earlier, then everything seemed to work perfectly fine even
> with those allocations failing.
> 
> I assume that setting rq->data_ring.desc_size to zero in
> vmxnet3_rq_destroy_all_rxdataring is also needed for the data_ring that
> faild to allocate its base. Otherwise it will later on be handed over
> to Vmxnet3_RxQueueConf->rxDataRingDescSize in the function
> vmxnet3_setup_driver_shared thus allowing to reference the data_ring of
> this rx_queue, but I didn't have time to pursue it any further.

I see, the new stack trace makes sense.
I'm guessing hypervisor decides whether feature is enabled or not based
on the ring size, not the ring address.

Please respin with the updated commit message (stack trace, Fixes tag,
explanation).

      reply	other threads:[~2024-05-30 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 10:06 [PATCH] vmxnet3: disable rx data ring on dma allocation failure Matthias Stocker
2024-05-30  0:57 ` Jakub Kicinski
2024-05-30 16:00   ` Matthias Stocker
2024-05-30 22:17     ` Jakub Kicinski [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=20240530151749.7118e4da@kernel.org \
    --to=kuba@kernel.org \
    --cc=doshir@vmware.com \
    --cc=mstocker@barracuda.com \
    --cc=netdev@vger.kernel.org \
    --cc=pv-drivers@vmware.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).