From: Octavian Purdila <opurdila@ixiacom.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, Leonard Crestez <lcrestez@ixiacom.com>
Subject: Re: [PATCH net-2.6] net: fix nulls list corruptions in sk_prot_alloc
Date: Tue, 14 Dec 2010 18:30:47 +0200 [thread overview]
Message-ID: <201012141830.47958.opurdila@ixiacom.com> (raw)
In-Reply-To: <1292343557.5934.22.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tuesday 14 December 2010, 18:19:17
> Hmm very good catch, but why a so invasive patch ?
>
> Only udp needs a special care.
>
> Other protocols could use the default 'cleaner', you dont need to force
> them to use the default ;)
>
Ah, OK now I get it. I thought that for protocols using non nulls lists we
must clear .next but I now see that we can skip that.
So default cleaner can be the nulls cleaner and portaddr cleaner will be used
for UDP and UDP lite. I'll rework the patch and post a new version.
prev parent reply other threads:[~2010-12-14 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 15:44 [PATCH net-2.6] net: fix nulls list corruptions in sk_prot_alloc Octavian Purdila
2010-12-14 16:19 ` Eric Dumazet
2010-12-14 16:30 ` Octavian Purdila [this message]
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=201012141830.47958.opurdila@ixiacom.com \
--to=opurdila@ixiacom.com \
--cc=eric.dumazet@gmail.com \
--cc=lcrestez@ixiacom.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