All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasily Averin <vvs@virtuozzo.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 0/3] rtnl_lock fixes
Date: Tue, 07 Jul 2015 18:53:28 +0300	[thread overview]
Message-ID: <559BF5F8.2000500@virtuozzo.com> (raw)

While investigation possible reasons of net_todo_list corruption 
on rhel6 based OpenVZ kernel I've found few places not fixed in mainline.

Vasily Averin (3):
  missing rtnl_unlock in i40evf_resume()
  missing rtnl_unlock in igb_sriov_reinit()
  ipmr_free_table() should be called under taken rtnl_lock

 drivers/net/ethernet/intel/i40evf/i40evf_main.c | 1 +
 drivers/net/ethernet/intel/igb/igb_main.c       | 1 +
 net/ipv6/ip6mr.c                                | 2 ++
 3 files changed, 4 insertions(+)

-- 
1.9.1


WARNING: multiple messages have this Message-ID (diff)
From: Vasily Averin <vvs@virtuozzo.com>
To: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org
Subject: [PATCH 0/3] rtnl_lock fixes
Date: Tue, 07 Jul 2015 18:53:28 +0300	[thread overview]
Message-ID: <559BF5F8.2000500@virtuozzo.com> (raw)

While investigation possible reasons of net_todo_list corruption 
on rhel6 based OpenVZ kernel I've found few places not fixed in mainline.

Vasily Averin (3):
  missing rtnl_unlock in i40evf_resume()
  missing rtnl_unlock in igb_sriov_reinit()
  ipmr_free_table() should be called under taken rtnl_lock

 drivers/net/ethernet/intel/i40evf/i40evf_main.c | 1 +
 drivers/net/ethernet/intel/igb/igb_main.c       | 1 +
 net/ipv6/ip6mr.c                                | 2 ++
 3 files changed, 4 insertions(+)

-- 
1.9.1

             reply	other threads:[~2015-07-07 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 15:53 Vasily Averin [this message]
2015-07-07 15:53 ` [PATCH 0/3] rtnl_lock fixes Vasily Averin
2015-07-08 23:15 ` [Intel-wired-lan] " David Miller
2015-07-08 23:15   ` David Miller
2015-07-08 23:23   ` [Intel-wired-lan] " Jeff Kirsher
2015-07-08 23:23     ` Jeff Kirsher

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=559BF5F8.2000500@virtuozzo.com \
    --to=vvs@virtuozzo.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.