From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, vineethp@amazon.com,
wei.liu2@citrix.com, paul.durrant@citrix.com,
stable@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()
Date: Thu, 9 Feb 2017 08:42:59 -0500 [thread overview]
Message-ID: <fa4ea104-4283-e707-019e-dee89dc66f3e@oracle.com> (raw)
In-Reply-To: <bc3bf927-568e-043a-2785-16e6c3628359@suse.com>
On 02/03/2017 04:38 AM, Juergen Gross wrote:
> On 30/01/17 18:45, Boris Ostrovsky wrote:
>> rx_refill_timer should be deleted as soon as we disconnect from the
>> backend since otherwise it is possible for the timer to go off before
>> we get to xennet_destroy_queues(). If this happens we may dereference
>> queue->rx.sring which is set to NULL in xennet_disconnect_backend().
>>
>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> CC: stable@vger.kernel.org
>
> Reviewed-by: Juergen Gross <jgross@suse.com>
David,
Are you going to take this to your tree or would you rather it goes via
Xen tree?
And the same question for
https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00625.html
and
https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00754.html
(And while I am at it, I took
https://lists.xenproject.org/archives/html/xen-devel/2017-01/msg00833.html
to Xen tree, hope you don't mind)
-boris
next prev parent reply other threads:[~2017-02-09 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 17:45 [PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend() Boris Ostrovsky
2017-01-30 18:07 ` Eric Dumazet
2017-01-30 18:23 ` Boris Ostrovsky
2017-01-30 19:06 ` Eric Dumazet
2017-01-30 19:31 ` Boris Ostrovsky
2017-01-31 17:47 ` Boris Ostrovsky
2017-02-01 23:29 ` Boris Ostrovsky
2017-02-02 0:01 ` Eric Dumazet
2017-02-03 9:38 ` Juergen Gross
2017-02-09 13:42 ` Boris Ostrovsky [this message]
2017-02-10 18:46 ` David Miller
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=fa4ea104-4283-e707-019e-dee89dc66f3e@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=stable@vger.kernel.org \
--cc=vineethp@amazon.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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