From: Jeff Dike <jdike@addtoit.com>
To: Steve Schmidtke <steve_schmidtke@hotmail.com>
Cc: blaisorblade@yahoo.it, kraxel@bytesex.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] RE: uml_switch security fixing
Date: Sat, 12 Mar 2005 00:48:08 -0500 [thread overview]
Message-ID: <200503120548.j2C5m8Jp006911@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 07 Mar 2005 04:42:19 GMT." <BAY24-F21573D60D3DDE776FDC27C835F0@phx.gbl>
steve_schmidtke@hotmail.com said:
> Attached are two patches. The first one, uml_net-slip.diff, is the
> minimal patch to apply to uml_net. The second one, uml_net-uml.diff,
> applies to 2.4.27-1um (note the half-hearted attempt to plug a FD
> leak in there as well). As a nice bonus, a UML with this patch still
> works with an unpatched uml_net binary.
Thanks, applied except for the slip_tramp() bit, which I already had.
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-03-12 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 4:42 [uml-devel] RE: uml_switch security fixing Steve Schmidtke
2005-03-09 10:34 ` Blaisorblade
2005-03-09 18:53 ` Steve Schmidtke
2005-03-09 19:31 ` Blaisorblade
2005-03-12 5:48 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-02 14:53 [uml-devel] " Blaisorblade
2005-03-03 12:47 ` [uml-devel] " Nuutti Kotivuori
2005-03-09 9:23 ` Blaisorblade
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=200503120548.j2C5m8Jp006911@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=kraxel@bytesex.org \
--cc=steve_schmidtke@hotmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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