All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: syzbot <syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	Dmitry Vyukov <dvyukov@google.com>,
	syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: [PATCH net 0/2] Fix two further potential unbounded recursions in GUE error handlers
Date: Thu,  3 Jan 2019 21:43:33 +0100	[thread overview]
Message-ID: <cover.1546547862.git.sbrivio@redhat.com> (raw)

Patch 1/2 takes care of preventing the issue fixed by commit 11789039da53
("fou: Prevent unbounded recursion in GUE error handler") also with
UDP-Lite payloads -- I just realised this might happen from a syzbot
report.

Patch 2/2 fixes the issue for both UDP and UDP-Lite on IPv6, which I also
forgot to deal with in that same commit.

Stefano Brivio (2):
  fou: Prevent unbounded recursion in GUE error handler also with
    UDP-Lite
  fou6: Prevent unbounded recursion in GUE error handler

 net/ipv4/fou.c  | 3 ++-
 net/ipv6/fou6.c | 8 ++++++++
 2 files changed, 10 insertions(+), 1 deletion(-)

-- 
2.20.1


             reply	other threads:[~2019-01-03 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 20:43 Stefano Brivio [this message]
2019-01-03 20:43 ` [PATCH net 1/2] fou: Prevent unbounded recursion in GUE error handler also with UDP-Lite Stefano Brivio
2019-01-03 20:43 ` [PATCH net 2/2] fou6: Prevent unbounded recursion in GUE error handler Stefano Brivio
2019-01-04 21:06 ` [PATCH net 0/2] Fix two further potential unbounded recursions in GUE error handlers 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=cover.1546547862.git.sbrivio@redhat.com \
    --to=sbrivio@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+4ad25edc7a33e4ab91e0@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=yoshfuji@linux-ipv6.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.