public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen•de>
To: syzbot <syzbot+7ee59ac26bbfbd823f1f@syzkaller•appspotmail.com>
Cc: coreteam@netfilter•org, davem@davemloft•net, fw@strlen•de,
	kadlec@blackhole•kfki.hu, linux-kernel@vger•kernel.org,
	netdev@vger•kernel.org, netfilter-devel@vger•kernel.org,
	pablo@netfilter•org, syzkaller-bugs@googlegroups•com
Subject: Re: general protection fault in nf_tables_dump_obj_done
Date: Thu, 4 Jan 2018 18:16:28 +0100	[thread overview]
Message-ID: <20180104171628.GA26320@breakpoint.cc> (raw)
In-Reply-To: <001a113fd5b81b33e40561f63c7a@google.com>

#syz fix: netfilter: nf_tables: fix potential NULL-ptr deref in nf_tables_dump_obj_done()

      reply	other threads:[~2018-01-04 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 16:58 general protection fault in nf_tables_dump_obj_done syzbot
2018-01-04 17:16 ` Florian Westphal [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=20180104171628.GA26320@breakpoint.cc \
    --to=fw@strlen$(echo .)de \
    --cc=coreteam@netfilter$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=kadlec@blackhole$(echo .)kfki.hu \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=netfilter-devel@vger$(echo .)kernel.org \
    --cc=pablo@netfilter$(echo .)org \
    --cc=syzbot+7ee59ac26bbfbd823f1f@syzkaller$(echo .)appspotmail.com \
    --cc=syzkaller-bugs@googlegroups$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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