From: Gary Thomas <gary@mlbassoc.com>
To: Larice Robert <larice@vidisys.de>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] mbuf leakage in if_i82559.c ?
Date: Thu, 20 Nov 2003 13:41:00 -0000 [thread overview]
Message-ID: <1069335681.1961.638.camel@hermes> (raw)
In-Reply-To: <200311201234.hAKCYnK17016@doms.vidisys.com>
On Thu, 2003-11-20 at 05:34, Larice Robert wrote:
> Hello,
>
> i think there is possible mbuf leakage in if_i82559.c
> could you please verify this ?
>
> as far as i understand this, eth_drv.c hands over responsibility for mbufs
> to if_i82559.c with the parameter key of the function i82559_send(...key...)
>
> later if_i82599.c gives them back to eth_drv.c with the parameter key
> of the function eth_drv_tx_done(...key...)
>
> BUT, when i82559_send thinks its queue is full, it will simply drop this
> key. is this ok ? is there somewhere another cleanup mechanism which
> i've not seen so far ?
>
This would be a leak - if it could happen. However, it should never
happen since the XXX_send() routine will only be called if the
XXX_can_send() routine says that the device has space. So if there
*is* space, then the packet would not be dropped, so there is no leak.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-11-20 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 12:35 Larice Robert
2003-11-20 13:41 ` Gary Thomas [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=1069335681.1961.638.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=larice@vidisys.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).