netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>,
	critson@perlfu.co.uk, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [BKPATCH] Re: [PATCH][2.5.22] OOPS in tcp_v6_get_port
Date: Tue, 18 Jun 2002 01:15:39 -0300	[thread overview]
Message-ID: <aemcaa$567$2@main.gmane.org> (raw)
In-Reply-To: <20020618035804.GA18759@conectiva.com.br>

Em Tue, Jun 18, 2002 at 12:58:04AM -0300, Arnaldo C. Melo escreveu:
> Em Mon, Jun 17, 2002 at 11:49:34PM -0300, Arnaldo C. Melo escreveu:
> > Em Mon, Jun 17, 2002 at 07:17:26PM -0700, David S. Miller escreveu:
> > >    From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
> > >    Date: Mon, 17 Jun 2002 21:57:35 -0300
> > > 
> > >    --- orig/net/ipv6/tcp_ipv6.c	Sat May 25 23:13:56 2002
> > >    +++ linux/net/ipv6/tcp_ipv6.c	Fri Jun 14 23:23:07 2002
> > > 
> > > I've installed this change into my tree in the meantime.
> > > If we find a better fix, we can just revert this.
> > 
> > OK, I found a better fix, I think, that allowed me to kill inet6_sk_generic
> > in af_inet6.c, using a constructor for the tcpv6, udpv6 and raw6 slab caches,
> > as suggested by Russel King, I'll be sending RSN.
> 
> Here it is, David, please consider pulling it from:
> 
> http://kernel-acme.bkbits.net:8080/tcpv6-pinet6
> 
> Best Regards,
> 
> - Arnaldo

Oops, brain fart, David, please don't apply, in tcp_create_openreq_child
we overwrite the ->pinet6 field after the constructor inits it to the proper
value :( Please leave the old patch in place for a while... :(

- Arnaldo

  parent reply	other threads:[~2002-06-18  4:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 20:26 [PATCH][2.5.22] OOPS in tcp_v6_get_port Carl Ritson
2002-06-17 21:33 ` David S. Miller
     [not found] ` <20020617.143319.54623892.davem@redhat.com>
2002-06-18  0:57   ` Arnaldo Carvalho de Melo
2002-06-18  2:17     ` David S. Miller
     [not found]     ` <20020617.191726.55300824.davem@redhat.com>
2002-06-18  2:49       ` Arnaldo Carvalho de Melo
2002-06-18  3:58         ` [BKPATCH] " Arnaldo Carvalho de Melo
     [not found]         ` <20020618035804.GA18759@conectiva.com.br>
2002-06-18  4:15           ` Arnaldo Carvalho de Melo [this message]
     [not found]           ` <20020618041539.GB18759@conectiva.com.br>
2002-06-18  4:17             ` David S. Miller
2002-06-18  7:38     ` Carl Ritson
2002-06-18  9:43   ` kuznet
2002-06-18  9:58     ` David S. Miller
2002-06-19  9:54       ` Arnaldo Carvalho de Melo
2002-06-18 11:51 ` net/ipv6/exthdrs.c Andras Kis-Szabo
2002-06-18 12:00   ` net/ipv6/exthdrs.c Pekka Savola
2002-06-18 13:50     ` net/ipv6/exthdrs.c Andras Kis-Szabo
2002-06-18 14:00       ` [PATCH] net/ipv6/exthdrs.c Andras Kis-Szabo
2002-06-18 19:03   ` net/ipv6/exthdrs.c kuznet
     [not found]     ` <1024435482.1332.10.camel@arwen>
2002-06-19  9:30       ` net/ipv6/exthdrs.c Kis-Szabo Andras
2002-06-19  9:42         ` net/ipv6/exthdrs.c kuznet

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='aemcaa$567$2@main.gmane.org' \
    --to=acme@conectiva.com.br \
    --cc=critson@perlfu.co.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=torvalds@transmeta.com \
    /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).