netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: Fix sock freeing before sock_init_data() with __sk_free()
Date: Mon, 31 Aug 2009 07:25:59 +0000	[thread overview]
Message-ID: <20090831072559.GD5005@ff.dom.local> (raw)
In-Reply-To: <4A9B7956.40507@gmail.com>

On Mon, Aug 31, 2009 at 09:18:46AM +0200, Eric Dumazet wrote:
> Jarek Poplawski a écrit :
> > On Mon, Aug 31, 2009 at 08:50:25AM +0200, Eric Dumazet wrote:
...
> >> Well, patch is yours, not mine, and I am confident it is OK.
> > 
> > Well, it's from you, and I guess you'll sign off too, but if you
> > think so...
> >  
> > Signed-off-by: Jarek Poplawski <jarkao2@gmail.com>
> > 
> > Thanks,
> > Jarek P.
> > 
> 
> Give me a few hours to review sk_alloc() call sites, test patch and officially submit it.
> 
> Thanks

Hmm... but you're "confident it is OK"?! (You know, I could've risked
my life or something... ;-)

Jarek P.

  reply	other threads:[~2009-08-31  7:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 22:23 [PATCH] net: Fix sock freeing before sock_init_data() with __sk_free() Jarek Poplawski
2009-08-31  6:26 ` Eric Dumazet
2009-08-31  6:36   ` Jarek Poplawski
2009-08-31  6:50     ` Eric Dumazet
2009-08-31  7:07       ` Jarek Poplawski
2009-08-31  7:18         ` Eric Dumazet
2009-08-31  7:25           ` Jarek Poplawski [this message]
2009-08-31  9:15           ` [PATCH] net: sk_free() should be allowed right after sk_alloc() Eric Dumazet
2009-08-31  9:30             ` Jarek Poplawski
2009-08-31 12:02               ` David Miller
2009-08-31 12:12                 ` Eric Dumazet
2009-09-02  0:50                   ` David Miller

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=20090831072559.GD5005@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.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 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).