All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 4/6] fm10k: reset Tx FIFO head and tail pointers as part of reset_work
Date: Wed, 24 Jun 2015 20:03:22 +0000	[thread overview]
Message-ID: <1435176202.17626.12.camel@intel.com> (raw)
In-Reply-To: <1434405656-10465-4-git-send-email-jacob.e.keller@intel.com>

On Mon, 2015-06-15 at 15:00 -0700, Jacob Keller wrote:
> This patch fixes a corner case issue with the PF/VF mailbox code.
> Currently, fm10k_mbx_reset_work clears various state about the
> mailbox. However, it did not clear the Tx FIFO head/tail pointers. 
> Thus,
> when the PF finally re-connects (say due to VF reset), it in
> -advertently
> might send some previous data in the Tx FIFO again. This was 
> discovered
> by attempting to perform a static VF MAC address assignment on the PF
> device. The VF would receive the message and then initiate a reset.
> During this process it disconnects and reconnects to the mailbox. If 
> the
> PF doesn't respond fast enough, it may not see the disconnect 
> message,
> and only sees a new connect message. In this flow, it does not 
> properly
> clear the Tx FIFO pointers. Thus, it will re-transmit the last 
> message
> in the Tx FIFO. However, it does not increment the mailbox Tx 
> messages
> because it has already reset mbx->pulled and thus does not think it 
> is
> actually sending any data. The fix is to simply reset the Tx FIFO
> pointers whenever we call fm10k_mbx_reset_work.
> 
> As a consequence, we no longer need both fm10k_mbx_fifo_drop_all and 
> calls
> to fm10k_mbx_update_max_size with a size of 0.

This patch will need a revision 2. There is some other issues this
patch creates which we need to properly resolve.

Clearing the Tx FIFO causes us to potentially drop untransmitted work
and thus fail to send repsonses with no error indication returning to
the base driver code.

I am working on a corrected fix now.

Regards,
Jake

  reply	other threads:[~2015-06-24 20:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 22:00 [Intel-wired-lan] [PATCH 1/6] fm10k: disable service task during suspend Jacob Keller
2015-06-15 22:00 ` [Intel-wired-lan] [PATCH 2/6] [TRIVIAL] fm10k: remove comment about rtnl_lock around mbx operations Jacob Keller
2015-09-02  1:56   ` Singh, Krishneil K
2015-09-02  2:16   ` Singh, Krishneil K
2015-06-15 22:00 ` [Intel-wired-lan] [PATCH 3/6] fm10k: only prevent removal of default VID rules Jacob Keller
2015-09-02  1:57   ` Singh, Krishneil K
2015-09-02  2:17   ` Singh, Krishneil K
2015-06-15 22:00 ` [Intel-wired-lan] [PATCH 4/6] fm10k: reset Tx FIFO head and tail pointers as part of reset_work Jacob Keller
2015-06-24 20:03   ` Keller, Jacob E [this message]
2015-06-15 22:00 ` [Intel-wired-lan] [PATCH 5/6] fm10k: update fm10k_slot_warn to use pcie_get_minimum link Jacob Keller
2015-06-19  2:22   ` Alexander Duyck
2015-06-19 15:31     ` Keller, Jacob E
2015-09-02  1:58   ` Singh, Krishneil K
2015-09-02  2:18   ` Singh, Krishneil K
2015-06-15 22:00 ` [Intel-wired-lan] [PATCH 6/6] fm10k: update netdev perm_addr during reinit, instead of at up Jacob Keller
2015-09-02  1:59   ` Singh, Krishneil K
2015-09-02  2:18   ` Singh, Krishneil K
2015-09-02  1:55 ` [Intel-wired-lan] [PATCH 1/6] fm10k: disable service task during suspend Singh, Krishneil K
2015-09-02  2:16 ` Singh, Krishneil K

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=1435176202.17626.12.camel@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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.