netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Florian Westphal <fw@strlen.de>
Cc: <xiyou.wangcong@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec 0/7] xfrm: policy: fix various bugs
Date: Thu, 10 Jan 2019 09:09:29 +0100	[thread overview]
Message-ID: <20190110080929.GL3581@gauss3.secunet.de> (raw)
In-Reply-To: <20190104131705.9550-1-fw@strlen.de>

On Fri, Jan 04, 2019 at 02:16:58PM +0100, Florian Westphal wrote:
> This series addresses various bugs, mostly fallout from the recent
> rcu tree work. One is a fix for an older bug coming from the initial
> rcu conversion.
> 
> There were several xfrm policy related syzbot bugs recently, but
> so far only one of them has a reproducer (addressed by patch #4).
> 
> As I provided ample rope for syzbot to hang itself with, there is
> some chance that this and the other fixes also resolve the KASAN
> and UAF syzbot xfrm reports reported in the last couple of days.
> 
> My plan is to wait until these patches are applied, and then tell syzbot
> for all the open reports that the last patch 'fixes this'.
> 
> AFAIU that will make syzbot report the problem again in case it can still
> trigger similar splats with these fixes in place.
> 
> Florian Westphal (7):
>       selftests: xfrm: add block rules with adjacent/overlapping subnets
>       xfrm: policy: use hlist rcu variants on inexact insert, part 2
>       xfrm: policy: increment xfrm_hash_generation on hash rebuild
>       xfrm: policy: delete inexact policies from inexact list on hash rebuild
>       xfrm: policy: fix reinsertion on node merge
>       selftests: xfrm: alter htresh to trigger move of policies to hash table
>       xfrm: policy: fix infinite loop when merging src-nodes

All applied, thanks a lot Florian!

      parent reply	other threads:[~2019-01-10  8:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 13:16 [PATCH ipsec 0/7] xfrm: policy: fix various bugs Florian Westphal
2019-01-04 13:16 ` [PATCH ipsec 1/7] selftests: xfrm: add block rules with adjacent/overlapping subnets Florian Westphal
2019-01-04 13:17 ` [PATCH ipsec 2/7] xfrm: policy: use hlist rcu variants on inexact insert, part 2 Florian Westphal
2019-01-04 13:17 ` [PATCH ipsec 3/7] xfrm: policy: increment xfrm_hash_generation on hash rebuild Florian Westphal
2019-01-04 13:17 ` [PATCH ipsec 4/7] xfrm: policy: delete inexact policies from inexact list " Florian Westphal
2019-01-05  4:46   ` Cong Wang
2019-01-05  9:53     ` Florian Westphal
2019-01-04 13:17 ` [PATCH ipsec 5/7] xfrm: policy: fix reinsertion on node merge Florian Westphal
2019-01-05  4:48   ` Cong Wang
2019-01-05  9:57     ` Florian Westphal
2019-01-04 13:17 ` [PATCH ipsec 6/7] selftests: xfrm: alter htresh to trigger move of policies to hash table Florian Westphal
2019-01-04 13:17 ` [PATCH ipsec 7/7] xfrm: policy: fix infinite loop when merging src-nodes Florian Westphal
2019-01-05  4:49   ` Cong Wang
2019-01-05  9:59     ` Florian Westphal
2019-01-09 13:03       ` Steffen Klassert
2019-01-10  8:09 ` Steffen Klassert [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=20190110080929.GL3581@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.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 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).