All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Phil Oester <kernel@linuxace.com>
Cc: Patrick McHardy <kaber@trash.net>,
	netdev@vger.kernel.org, Denis Lunev <den@openvz.org>
Subject: Re: 2.6.25-rc: Null dereference in ip_defrag
Date: Tue, 18 Mar 2008 10:53:53 +0300	[thread overview]
Message-ID: <47DF7511.5080502@openvz.org> (raw)
In-Reply-To: <20080317194014.GA7302@linuxace.com>

Phil Oester wrote:
> On Mon, Mar 17, 2008 at 06:43:32PM +0100, Patrick McHardy wrote:
>> Pavel Emelyanov wrote:
>>> Can you check with this patch, please (untested, but should work)?
>> This is getting pretty ugly. Shouldn't
>>
>> int ip_defrag(struct sk_buff *skb, u32 user)
>> {
>> ...
>> -         net = skb->dev->nd_net;
>> +         net = skb->dev ? skb->dev->nd_net : skb->dst->dev->nd_net;
>>
>> work as well?

It will, though I do not like such implicit decisions.

> I can try either patch, but Patrick's looks simpler and thus perhaps
> a better candidate this late in the -rc stage.
> 
> Pavel - you concur?

No one, except for a complaint, that we (me and Denis) warned other
net namespaces developers that getting a struct net from function
arguments, sockets, dst entries, devices, etc. is going to become a
pain in the ... anyway. We proposed to create current_net macro, that
would give us a correct net in any place... Such thing would allow us
to avoid this problem. But I'm afraid, that it's just too late to
change the model :(

> Phil
> 


  reply	other threads:[~2008-03-18  7:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 17:00 2.6.25-rc: Null dereference in ip_defrag Phil Oester
2008-03-17 17:40 ` Pavel Emelyanov
2008-03-17 17:43   ` Patrick McHardy
2008-03-17 17:57     ` Denis V. Lunev
2008-03-17 17:51       ` Patrick McHardy
2008-03-17 19:40     ` Phil Oester
2008-03-18  7:53       ` Pavel Emelyanov [this message]
2008-03-18  9:51         ` Pavel Emelyanov
2008-03-20  0:39           ` Phil Oester
2008-03-20 14:47             ` Patrick McHardy
2008-03-20 15:30               ` Phil Oester
2008-03-20 15:33                 ` Patrick McHardy

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=47DF7511.5080502@openvz.org \
    --to=xemul@openvz.org \
    --cc=den@openvz.org \
    --cc=kaber@trash.net \
    --cc=kernel@linuxace.com \
    --cc=netdev@vger.kernel.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.