stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Daniel Jurgens <danielj@mellanox.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	Saeed Mahameed <saeedm@mellanox.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>
Subject: Re: Patch "net/mlx5: Cancel recovery work in remove flow" has been added to the 4.9-stable tree
Date: Fri, 13 Jan 2017 08:45:32 +0100	[thread overview]
Message-ID: <20170113074532.GB16934@kroah.com> (raw)
In-Reply-To: <VI1PR0501MB2429BC1AB9E0491EB8FD8CD0C4790@VI1PR0501MB2429.eurprd05.prod.outlook.com>

On Thu, Jan 12, 2017 at 09:00:28PM +0000, Daniel Jurgens wrote:
> On 1/12/2017 2:39 PM, gregkh@linuxfoundation.org wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> >     net/mlx5: Cancel recovery work in remove flow
> >
> > to the 4.9-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> >      net-mlx5-cancel-recovery-work-in-remove-flow.patch
> > and it can be found in the queue-4.9 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From foo@baz Thu Jan 12 21:37:26 CET 2017
> > From: Daniel Jurgens <danielj@mellanox.com>
> > Date: Wed, 28 Dec 2016 14:58:33 +0200
> > Subject: net/mlx5: Cancel recovery work in remove flow
> >
> > From: Daniel Jurgens <danielj@mellanox.com>
> >
> >
> > [ Upstream commit 689a248df83b6032edc57e86267b4e5cc8d7174e ]
> >
> > If there is pending delayed work for health recovery it must be canceled
> > if the device is being unloaded.
> >
> > Fixes: 05ac2c0b7438 ("net/mlx5: Fix race between PCI error handlers and health work")
> > Signed-off-by: Daniel Jurgens <danielj@mellanox.com>
> > Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
> > Signed-off-by: David S. Miller <davem@davemloft.net>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> >  drivers/net/ethernet/mellanox/mlx5/core/main.c |    5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > --- a/drivers/net/ethernet/mellanox/mlx5/core/main.c
> > +++ b/drivers/net/ethernet/mellanox/mlx5/core/main.c
> > @@ -1159,6 +1159,8 @@ static int mlx5_unload_one(struct mlx5_c
> >  {
> >  	int err = 0;
> >  
> > +	mlx5_drain_health_wq(dev);
> > +
> >  	mutex_lock(&dev->intf_state_mutex);
> >  	if (test_bit(MLX5_INTERFACE_STATE_DOWN, &dev->intf_state)) {
> >  		dev_warn(&dev->pdev->dev, "%s: interface is down, NOP\n",
> > @@ -1319,10 +1321,9 @@ static pci_ers_result_t mlx5_pci_err_det
> >  
> >  	mlx5_enter_error_state(dev);
> >  	mlx5_unload_one(dev, priv, false);
> > -	/* In case of kernel call save the pci state and drain health wq */
> > +	/* In case of kernel call save the pci state */
> >  	if (state) {
> >  		pci_save_state(pdev);
> > -		mlx5_drain_health_wq(dev);
> >  		mlx5_pci_disable_device(dev);
> >  	}
> >  
> >
> >
> > Patches currently in stable-queue which might be from danielj@mellanox.com are
> >
> > queue-4.9/net-mlx5-cancel-recovery-work-in-remove-flow.patch
> >
> This patch introduced a bug.  Please take this one with it: https://patchwork.ozlabs.org/patch/713425/

Ick.  David, should I drop this from the queue now, or just wait a day
and pick this one up too if it hits Linus's tree?  Any suggestions?

thanks,

greg k-h

      reply	other threads:[~2017-01-13  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 20:38 Patch "net/mlx5: Cancel recovery work in remove flow" has been added to the 4.9-stable tree gregkh
2017-01-12 21:00 ` Daniel Jurgens
2017-01-13  7:45   ` gregkh [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=20170113074532.GB16934@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=danielj@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=saeedm@mellanox.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.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 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).