From: Arjan van de Ven <arjan@infradead.org>
To: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Wright <chrisw@osdl.org>,
netdev@oss.sgi.com, Hank Leininger <hlein@progressive-comp.com>
Subject: Re: [PATCH] OpenBSD Networking-related randomization port
Date: Fri, 28 Jan 2005 21:47:45 +0100 [thread overview]
Message-ID: <1106945266.7776.41.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1106944492.3864.30.camel@localhost.localdomain>
On Fri, 2005-01-28 at 21:34 +0100, Lorenzo Hernández García-Hierro
wrote:
> Hi,
>
> Attached the new patch following Arjan's recommendations.
> I'm sorry about not making it "inlined", but my mail agent messes up the
> diffs if I do so.
> Still waiting for the OSDL STP tests results, they will take a while to
> finish.
>
> Cheers,
lots better already! Some more comments (now that the patch got a lot
easier to read :)
static inline __u32 tcp_v4_init_sequence(struct sock *sk, struct
sk_buff *skb)
{
- return secure_tcp_sequence_number(skb->nh.iph->daddr,
- skb->nh.iph->saddr,
- skb->h.th->dest,
- skb->h.th->source);
+
+ return ip_randomisn();
}
is there a reason for the weird indentation?
+ if (!tp->write_seq) {
+ tp->write_seq = ip_randomisn();
+ }
spare { } pare that's not needed, also looks like one tab too many
as for obsd_get_random_long().. would it be possible to use the
get_random_int() function from the patches I posted the other day? They
use the existing random.c infrastructure instead of making a copy...
I still don't understand why you need a obsd_rand.c and can't use the
normal random.c
static inline u32 xprt_alloc_xid(struct rpc_xprt *xprt)
{
- return xprt->xid++;
+ /* Return randomized xprt->xid instead of prt->xid++ */
+ return (u32) obsd_get_random_long();
+
}
that cast looks quite redundant...
next prev parent reply other threads:[~2005-01-28 20:56 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 17:17 Lorenzo Hernández García-Hierro
2005-01-28 17:40 ` Adrian Bunk
2005-01-28 17:47 ` Lorenzo Hernández García-Hierro
2005-01-28 18:18 ` Stephen Hemminger
2005-01-28 18:54 ` Lorenzo Hernández García-Hierro
2005-01-28 19:09 ` Adrian Bunk
2005-01-28 18:02 ` Stephen Hemminger
2005-01-28 18:31 ` Lorenzo Hernández García-Hierro
2005-01-28 18:52 ` Stephen Hemminger
2005-01-28 18:58 ` Lorenzo Hernández García-Hierro
2005-01-28 20:34 ` Lorenzo Hernández García-Hierro
2005-01-28 20:45 ` David S. Miller
2005-01-28 21:34 ` Stephen Hemminger
2005-01-28 21:45 ` David S. Miller
2005-01-29 6:59 ` Andi Kleen
2005-01-28 20:47 ` Arjan van de Ven [this message]
2005-01-28 22:12 ` Lorenzo Hernández García-Hierro
2005-01-29 8:04 ` Arjan van de Ven
2005-01-29 8:05 ` Arjan van de Ven
2005-01-29 9:15 ` Valdis.Kletnieks
2005-01-31 16:50 ` Adrian Bunk
2005-01-31 17:23 ` Lorenzo Hernández García-Hierro
2005-01-31 20:11 ` Ingo Molnar
2005-01-31 23:27 ` linux
2005-02-12 22:29 ` Andi Kleen
2005-02-12 23:25 ` linux
2005-02-13 0:18 ` Roland Dreier
2005-02-13 1:41 ` linux
2005-02-02 17:17 ` linux
2005-02-02 17:38 ` Lorenzo Hernández García-Hierro
2005-02-03 19:51 ` Stephen Hemminger
2005-02-03 20:14 ` Lennert Buytenhek
2005-01-31 19:42 ` Valdis.Kletnieks
2005-01-31 20:03 ` Lorenzo Hernández García-Hierro
2005-02-01 23:22 ` Matt Mackall
2005-01-28 18:04 ` Jörn Engel
2005-01-28 18:07 ` Arjan van de Ven
2005-01-28 18:36 ` Lorenzo Hernández García-Hierro
2005-02-01 14:54 ` Bill Davidsen
2005-01-28 19:24 ` Horst von Brand
2005-01-29 18:16 ` Florian Weimer
2005-01-28 19:24 Hank Leininger
2005-01-29 7:24 linux
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=1106945266.7776.41.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=chrisw@osdl.org \
--cc=hlein@progressive-comp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@gnu.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®