From: Koushik <raghavendra.koushik@s2io.com>
To: jgarzik@pobox.com, netdev@oss.sgi.com, kumarkr@us.ibm.com
Cc: rapuru.sriram@s2io.com, leonid.grossman@s2io.com,
alicia.pena@s2io.com, ravinandan.arakali@s2io.com,
raghavendra.koushik@s2io.com
Subject: [PATCH 2.6.9-rc2 1/1] S2io: fixes in free_shared_mem function
Date: Thu, 18 Nov 2004 13:35:06 -0800 (PST) [thread overview]
Message-ID: <20041118213506.1081C32887@linux.site> (raw)
Hello All,
As per KK's review comment received on Nov 8 about the free_shared_mem function, Iam sending the following patch.
The change log includes:
1. Break from the main 'for loop' if ba[i] is NULL.
2. In the second level 'for loop', if ba[i][j] is NULL, instead of
continuing as was done previously, we now free the ba[i] pointer and
break from the main 'for loop'.
3. In the 'while loop' inside the second tier 'for loop', if any of the
three pointers (ba or ba->ba_0_org or ba->ba_1_org) is found to be NULL,
then ba[i], ba[i][j] and the non NULL buffer pointer if any
(ba_0_org or ba_1_org) is freed and break from the main 'for loop'.
Signed-off-by: Koushik <raghavendra.koushik@s2io.com>
Signed-off-by: Ravi <ravinandan.arakali@s2io.com>
---
diff -urN vanilla_linux/drivers/net/s2io.c linux-2.6.8.1/drivers/net/s2io.c
--- vanilla_linux/drivers/net/s2io.c 2004-11-16 16:42:16.429560736 -0800
+++ linux-2.6.8.1/drivers/net/s2io.c 2004-11-18 10:07:47.553183896 -0800
@@ -560,21 +560,35 @@
for (i = 0; i < config->rx_ring_num; i++) {
blk_cnt =
config->rx_cfg[i].num_rxd / (MAX_RXDS_PER_BLOCK + 1);
+ if (!nic->ba[i])
+ goto end_free;
for (j = 0; j < blk_cnt; j++) {
int k = 0;
- if (!nic->ba[i][j])
- continue;
+ if (!nic->ba[i][j]) {
+ kfree(nic->ba[i]);
+ goto end_free;
+ }
while (k != MAX_RXDS_PER_BLOCK) {
buffAdd_t *ba = &nic->ba[i][j][k];
+ if (!ba || !ba->ba_0_org || !ba->ba_1_org)
+ {
+ kfree(nic->ba[i]);
+ kfree(nic->ba[i][j]);
+ if(ba->ba_0_org)
+ kfree(ba->ba_0_org);
+ if(ba->ba_1_org)
+ kfree(ba->ba_1_org);
+ goto end_free;
+ }
kfree(ba->ba_0_org);
kfree(ba->ba_1_org);
k++;
}
kfree(nic->ba[i][j]);
}
- if (nic->ba[i])
- kfree(nic->ba[i]);
+ kfree(nic->ba[i]);
}
+end_free:
#endif
if (mac_control->stats_mem) {
next reply other threads:[~2004-11-18 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 21:35 Koushik [this message]
2004-12-03 0:39 ` [PATCH 2.6.9-rc2 1/1] S2io: fixes in free_shared_mem function Ravinandan Arakali
2005-01-07 3:53 ` Jeff Garzik
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=20041118213506.1081C32887@linux.site \
--to=raghavendra.koushik@s2io.com \
--cc=alicia.pena@s2io.com \
--cc=jgarzik@pobox.com \
--cc=kumarkr@us.ibm.com \
--cc=leonid.grossman@s2io.com \
--cc=netdev@oss.sgi.com \
--cc=rapuru.sriram@s2io.com \
--cc=ravinandan.arakali@s2io.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).