From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: vvs@virtuozzo.com, netdev@vger.kernel.org,
intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH 0/3] rtnl_lock fixes
Date: Wed, 08 Jul 2015 16:23:43 -0700 [thread overview]
Message-ID: <1436397823.3214.15.camel@intel.com> (raw)
In-Reply-To: <20150708.161533.531768243562810631.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
On Wed, 2015-07-08 at 16:15 -0700, David Miller wrote:
> From: Vasily Averin <vvs@virtuozzo.com>
> Date: Tue, 07 Jul 2015 18:53:28 +0300
>
> > While investigation possible reasons of net_todo_list corruption
> > on rhel6 based OpenVZ kernel I've found few places not fixed in
> mainline.
>
> I'm assuming the Intel folks will pick these up
Correct, got them queued up.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-07-08 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 15:53 [PATCH 0/3] rtnl_lock fixes Vasily Averin
2015-07-08 23:15 ` David Miller
2015-07-08 23:23 ` Jeff Kirsher [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=1436397823.3214.15.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=vvs@virtuozzo.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).