From: David Miller <davem@davemloft.net>
To: baruch@tkos.co.il
Cc: lanconelli.claudio@eptar.com, jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] enc28j60: fix RX buffer overflow
Date: Sun, 04 Jan 2009 16:23:19 -0800 (PST) [thread overview]
Message-ID: <20090104.162319.207306783.davem@davemloft.net> (raw)
In-Reply-To: <20081230135539.GA10015@diamond.tkos.co.il>
From: Baruch Siach <baruch@tkos.co.il>
Date: Tue, 30 Dec 2008 15:55:39 +0200
> The enc28j60 driver doesn't check whether the length of the packet as reported
> by the hardware fits into the preallocated buffer. When stressed, the hardware
> may report insanely large packets even tough the "Receive OK" bit is set. Fix
> this.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Applied, thanks.
prev parent reply other threads:[~2009-01-05 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 13:55 [PATCH] enc28j60: fix RX buffer overflow Baruch Siach
2009-01-05 0:23 ` David Miller [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=20090104.162319.207306783.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=baruch@tkos.co.il \
--cc=jgarzik@pobox.com \
--cc=lanconelli.claudio@eptar.com \
--cc=netdev@vger.kernel.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 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).