All of lore.kernel.org
 help / color / mirror / Atom feed
From: Faidon Liambotis <paravoid@debian.org>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org
Subject: Re: Network stack status & bugs?
Date: Thu, 29 Oct 2020 03:34:20 +0200	[thread overview]
Message-ID: <20201029013420.GA1689@tty.gr> (raw)
In-Reply-To: <20201027211706.ojmfsa4rfhjl2x24@tomti.i.net-space.pl>

Hi Daniel,

On Tue, Oct 27, 2020 at 10:17:06PM +0100, Daniel Kiper wrote:
> On Mon, Jun 15, 2020 at 12:51:29PM +0300, Faidon Liambotis wrote:
> > Around a year ago, in my attempts to use GRUB for PXE, I ran into quite
> > a few bugs with GRUB's TCP, DNS and HTTP stack that prevented me from
> > using GRUB for that purpose.
> >
> > I tried my best to troubleshoot them and provide ways to reproduce them.
> > I posted my findings in Savannah:
> >   - https://savannah.gnu.org/bugs/?56391 TCP FSM bug(s)
> >   - https://savannah.gnu.org/bugs/?56390 Non-dual-stack aware DNS
> >   - https://savannah.gnu.org/bugs/?49531 HTTP Connection: close
> >
> > I haven't seen any activity in these for over a year, but that does not
> > seem to be unusual for bugs reported to Savannah in general(?).
> >
> > However, from what I can tell, this mailing list seems to be getting a
> > lot of activity and lots of progress being made (including recent e.g.
> > the recent UEFI IPv6 improvements, yay!). So, I'm giving this a go
> > instead in the hopes to surface those to the attention of more
> > knowledgeable folks :)
> 
> May I ask you to retest the latest upstream version from git master? I think
> we should fix at least some of theses issues for upcoming 2.06 release.

I can confirm that all three of those bugs are still present in current
tip (2df291226). Happy to help test any patches!

Regards,
Faidon


  reply	other threads:[~2020-10-29  1:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  9:51 Network stack status & bugs? Faidon Liambotis
2020-10-27 21:17 ` Daniel Kiper
2020-10-29  1:34   ` Faidon Liambotis [this message]
2020-11-16 21:04     ` Faidon Liambotis
2020-11-18 14:53       ` Daniel Kiper

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=20201029013420.GA1689@tty.gr \
    --to=paravoid@debian.org \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.