public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: warchild@spoofed.org
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: remote memory reading using arp?
Date: Sun, 28 Apr 2002 13:47:25 -0400	[thread overview]
Message-ID: <20020428174725.GA5399@spoofed.org> (raw)
In-Reply-To: <20020427202756.GC6240@spoofed.org.suse.lists.linux.kernel> <3CCB0EAB.9050602@ixiacom.com.suse.lists.linux.kernel> <p73znzom2kv.fsf@oldwotan.suse.de>

> The driver should be fixed in that case. I would consider it a driver
> bug. The cost of clearing the tail should be minimal, it is at most
> two cache lines.
> 
> Is it known which driver caused this?

My testing yesterday was done with a Xircom RBEM58G-100 (10/100 + 56k) and an
Aironet PC4800 (with xircom_tulip_cb and airo/airo_cs, respectively).
Since this may be a driver problem, I should note that the airo drivers are
from pcmcia-cs-3.1.33.

 
> > This is NOT a "remote memory reading" exploit, since there is no way to
> 
> It really is. 

I'm finding it really difficult to replicate this problem today, but if I
find anything else that may be of use to help shed more light on this
issue, I'll be sure and share it.

thanks

  reply	other threads:[~2002-04-28 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020427202756.GC6240@spoofed.org.suse.lists.linux.kernel>
     [not found] ` <3CCB0EAB.9050602@ixiacom.com.suse.lists.linux.kernel>
2002-04-28 12:26   ` remote memory reading using arp? Andi Kleen
2002-04-28 17:47     ` warchild [this message]
2002-04-29 15:24     ` Calin A. Culianu
2002-04-29 15:31       ` Andi Kleen
2002-04-30  3:04         ` warchild
2002-05-01 19:37         ` Dirty memory? (WAS Re: remote memory reading using arp?) Calin A. Culianu
2002-05-01 22:24           ` Calin A. Culianu
2002-04-27 20:27 remote memory reading using arp? Warchild
2002-04-27 20:48 ` Bryan Rittmeyer
2002-04-27 21:19   ` Warchild

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=20020428174725.GA5399@spoofed.org \
    --to=warchild@spoofed.org \
    --cc=ak@suse.de \
    --cc=linux-kernel@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