All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Wei Yongjun <yjwei@cn.fujitsu.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: xfrm: Fix initialize repl field of struct xfrm_state
Date: Mon, 21 Mar 2011 08:54:21 +0100	[thread overview]
Message-ID: <20110321075421.GA27581@secunet.com> (raw)
In-Reply-To: <4D86F4EA.6030909@cn.fujitsu.com>

Thanks for catching this!

On Mon, Mar 21, 2011 at 02:49:14PM +0800, Wei Yongjun wrote:
> > Ok, thanks for the explanation.
> >
> > I think there is a simple way out of this:
> >
> > 1) Rename current xfrm_init_state to __xfrm_init_state, add
> >    "bool init_replay" argument.  Add the xfrm_init_replay()
> >    call, as in your patch, but conditionalized on this boolean.
> >
> > 2) Implement xfrm_init_state as inline, which calls
> >    __xfrm_init_state(..., true)
> >
> > 3) Replace xfrm_init_state() call in xfrm_user.c with
> >    __xfrm_init_state(..., false)
> >
> > This seems to avoid all the problems.  We don't need to touch every
> > caller, and we avoid initializing the replay state twice in xfrm_user
> >
> > Ok?
> 
> This OK, I will do this change, thanks.
> 

This looks ok for me too. I just noticed that we also need to clone the
replay_esn/preplay_esn informations and to reinitialize the sequence
number counting on XFRM MIGRATE from the original state before we
call xfrm_init_replay.

I'll fix this up once your patch is applied.

Thanks,

Steffen

  reply	other threads:[~2011-03-21  7:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21  5:45 xfrm: Fix initialize repl field of struct xfrm_state Wei Yongjun
2011-03-21  5:48 ` [PATCH] " Wei Yongjun
2011-03-21  5:55 ` David Miller
2011-03-21  6:36   ` Wei Yongjun
2011-03-21  6:46     ` David Miller
2011-03-21  6:49       ` Wei Yongjun
2011-03-21  7:54         ` Steffen Klassert [this message]
2011-03-21  7:44       ` [PATCH v2] " Wei Yongjun
2011-03-21  8:00         ` David Miller
2011-03-21  8:01           ` David Miller
2011-03-21  8:37           ` [PATCH v3] " Wei Yongjun
2011-03-22  1:08             ` David Miller
2011-03-21  8:25       ` Steffen Klassert
2011-03-21  9:10         ` Wei Yongjun
2011-03-21  9:18           ` Wei Yongjun
2011-03-21 12:06             ` Steffen Klassert
2011-03-22  1:04               ` Wei Yongjun
2011-03-22 13:14                 ` Steffen Klassert

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=20110321075421.GA27581@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=yjwei@cn.fujitsu.com \
    /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.