From: Felix Manlunas <felix.manlunas@cavium.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, raghu.vatsavayi@cavium.com,
derek.chickles@cavium.com, satananda.burla@cavium.com,
ricardo.farrington@cavium.com
Subject: [PATCH net-next 0/3] LiquidIO: avoid VM low memory crashes
Date: Wed, 7 Jun 2017 20:50:45 -0700 [thread overview]
Message-ID: <20170608035045.GA1608@felix-thinkpad.cavium.com> (raw)
From: Rick Farrington <ricardo.farrington@cavium.com>
This patchset addresses issues brought about by low memory conditions
in a VM. These conditions were only seen when VM's were intentionally
created with small amounts of memory (for stress testing).
1. Fix GPF in octeon_init_droq(); zero the allocated block 'recv_buf_list'.
This prevents a GPF trying to access an invalid 'recv_buf_list[i]' entry
in octeon_droq_destroy_ring_buffers() if init didn't alloc all entries.
2. Don't dereference a NULL ptr in octeon_droq_destroy_ring_buffers().
3. For defensive programming, zero the allocated block 'oct->droq[0]' in
octeon_setup_output_queues() and 'oct->instr_queue[0]' in
octeon_setup_instr_queues().
drivers/net/ethernet/cavium/liquidio/octeon_device.c | 8 ++++----
drivers/net/ethernet/cavium/liquidio/octeon_droq.c | 6 ++++--
2 files changed, 8 insertions(+), 6 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-06-08 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 3:50 Felix Manlunas [this message]
2017-06-08 3:52 ` [PATCH net-next 1/3] LiquidIO: lowmem: init allocated memory to 0 Felix Manlunas
2017-06-08 3:52 ` [PATCH net-next 2/3] LiquidIO: lowmem: do not dereference NULL ptr Felix Manlunas
2017-06-08 3:53 ` [PATCH net-next 3/3] LiquidIO: lowmem: init allocated memory to 0 Felix Manlunas
2017-06-08 7:12 ` [PATCH net-next 0/3] LiquidIO: avoid VM low memory crashes Leon Romanovsky
2017-06-08 13:16 ` 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=20170608035045.GA1608@felix-thinkpad.cavium.com \
--to=felix.manlunas@cavium.com \
--cc=davem@davemloft.net \
--cc=derek.chickles@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=raghu.vatsavayi@cavium.com \
--cc=ricardo.farrington@cavium.com \
--cc=satananda.burla@cavium.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).