All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] net/sfc: add missing Rx descriptor status callback
Date: Wed, 30 May 2018 09:44:44 +0300	[thread overview]
Message-ID: <54455a54-fef1-8ad7-0bea-6c864bc4cbbe@solarflare.com> (raw)
In-Reply-To: <1527490247-23324-1-git-send-email-arybchenko@solarflare.com>

Thomas, Ferruh,

I've found out that the following patch is deferred in patchwork:
https://dpdk.org/dev/patchwork/patch/40455/

It is critical under certain conditions since fix application crash.
The patch is net/sfc local and just few lines - absolutely harmless.
The only potential DPDK-wide effect is build, but the patch is really
trivial and it is hard to imagine how it could affect the build.
I'd like it to be included in 18.05, if possible.

I understand that 18.05 is really very-very late already and it
could be too late even for such patch. Just would like to
double-check it.

Thanks,
Andrew.

On 05/28/2018 09:50 AM, Andrew Rybchenko wrote:
> Rx descriptor status callback was lost and request of the Rx
> descriptor status crashes application if equal stride super-buffer
> Rx mode is used.
>
> Fixes: 390f9b8d82c9 ("net/sfc: support equal stride super-buffer Rx mode")
>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
> ---
>   drivers/net/sfc/sfc_ef10_essb_rx.c | 9 +++++++++
>   1 file changed, 9 insertions(+)
>
> diff --git a/drivers/net/sfc/sfc_ef10_essb_rx.c b/drivers/net/sfc/sfc_ef10_essb_rx.c
> index 289b61e52..5f5af602c 100644
> --- a/drivers/net/sfc/sfc_ef10_essb_rx.c
> +++ b/drivers/net/sfc/sfc_ef10_essb_rx.c
> @@ -413,6 +413,14 @@ sfc_ef10_essb_rx_qdesc_npending(__rte_unused struct sfc_dp_rxq *dp_rxq)
>   	return -ENOTSUP;
>   }
>   
> +static sfc_dp_rx_qdesc_status_t sfc_ef10_essb_rx_qdesc_status;
> +static int
> +sfc_ef10_essb_rx_qdesc_status(__rte_unused struct sfc_dp_rxq *dp_rxq,
> +			      __rte_unused uint16_t offset)
> +{
> +	return -ENOTSUP;
> +}
> +
>   static sfc_dp_rx_get_dev_info_t sfc_ef10_essb_rx_get_dev_info;
>   static void
>   sfc_ef10_essb_rx_get_dev_info(struct rte_eth_dev_info *dev_info)
> @@ -687,5 +695,6 @@ struct sfc_dp_rx sfc_ef10_essb_rx = {
>   	.qpurge			= sfc_ef10_essb_rx_qpurge,
>   	.supported_ptypes_get	= sfc_ef10_supported_ptypes_get,
>   	.qdesc_npending		= sfc_ef10_essb_rx_qdesc_npending,
> +	.qdesc_status		= sfc_ef10_essb_rx_qdesc_status,
>   	.pkt_burst		= sfc_ef10_essb_recv_pkts,
>   };

  reply	other threads:[~2018-05-30  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28  6:50 [PATCH] net/sfc: add missing Rx descriptor status callback Andrew Rybchenko
2018-05-30  6:44 ` Andrew Rybchenko [this message]
2018-05-30  9:42   ` Ferruh Yigit
2018-05-30 10:30     ` Thomas Monjalon

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=54455a54-fef1-8ad7-0bea-6c864bc4cbbe@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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.