LKML Archive on
help / color / mirror / Atom feed
From: Paul Moore <>
Cc: Andrew Morton <>,,
Subject: Re: 2.6.24-rc6-mm1 - oddness with IPv4/v6 mapped sockets hanging...
Date: Mon, 14 Jan 2008 14:07:46 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Monday 14 January 2008 1:50:39 pm wrote:
> On Mon, 14 Jan 2008 13:22:10 EST, said:
> > Apparently the only new commit in there since the tree that was in
> > 24-rc6-mm1 is 5d95575903fd3865b884952bd93c339d48725c33 adding some
> > warning printk's.  Would it be more productive to test against the full
> > tree, or leaving out the one commit I already reverted?
> <voice=Emily Litella> Nevermind... </voice> :)
> The new commit won't apply with the other one reverted - it patches
> security/selinux/netnode.c which was created by the problematic commit...

There have been quite a few changes in lblnet-2.6_testing since 2.6.24-rc6-mm1 
so I would recommend taking the whole tree.  I'm also not quite sure if 
simply reverting the "Convert the netif code to use ifindex values" patch 
would solve the problem as there are other patches in the rc6-mm1 tree that 
rely on skb->iif being valid (new code, not converted code).  If you want to 
stick with a _relatively_ vanilla rc6-mm1 tree I would leave everything in 
and simply apply the following patch which solved the skb_clone()/iif 

paul moore
linux security @ hp

  reply	other threads:[~2008-01-14 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13  7:35 2.6.24-rc6-mm1 - oddness with IPv4/v6 mapped sockets hanging Valdis.Kletnieks
2008-01-13 21:46 ` Herbert Xu
2008-01-14 16:15 ` Valdis.Kletnieks
2008-01-14 16:36   ` Paul Moore
2008-01-14 18:05     ` Valdis.Kletnieks
2008-01-14 18:22       ` Valdis.Kletnieks
2008-01-14 18:50         ` Valdis.Kletnieks
2008-01-14 19:07           ` Paul Moore [this message]
2008-01-14 19:37             ` Valdis.Kletnieks
2008-01-14 20:02               ` Paul Moore
2008-01-14 23:04             ` Valdis.Kletnieks
2008-01-14 23:19               ` Paul Moore

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).