netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Jozsef Kadlecsik <kadlec@netfilter.org>,
	coreteam@netfilter.org, David Miller <davem@davemloft.net>,
	Marco Elver <elver@google.com>, Florian Westphal <fw@strlen.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Enrico Weigelt, metux IT consult" <info@metux.net>,
	jeremy@azazel.net, Kate Stewart <kstewart@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Netdev <netdev@vger.kernel.org>,
	NetFilter <netfilter-devel@vger.kernel.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: KASAN: slab-out-of-bounds Read in bitmap_ip_add
Date: Fri, 31 Jan 2020 13:06:56 -0800	[thread overview]
Message-ID: <CAHk-=wg4Vc-SVMzFE5fKy5AP1P0GTozP_vmDOCJuspcu9wxpjg@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpUO2s2j0gbjYp8J3Q7J-peLChxL71+tzR0d6SphMZ7Aiw@mail.gmail.com>

On Fri, Jan 31, 2020 at 1:02 PM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>
> It is supposed to be fixed by commit 32c72165dbd0

Ahh, thanks, I missed that. I actually looked at the current code and
saw the bitmap_zalloc() and it all looked fine, and assumed there was
some other bug in the elements calculation.

I didn't realize that it looked fine because it had already been fixed.

Thanks,
             Linus

  reply	other threads:[~2020-01-31 21:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19  2:07 KASAN: slab-out-of-bounds Read in bitmap_ip_add syzbot
2020-01-27  4:01 ` syzbot
2020-01-31 20:57   ` Linus Torvalds
2020-01-31 21:02     ` Cong Wang
2020-01-31 21:06       ` Linus Torvalds [this message]
2020-03-22 18:02 ` syzbot

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='CAHk-=wg4Vc-SVMzFE5fKy5AP1P0GTozP_vmDOCJuspcu9wxpjg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=elver@google.com \
    --cc=fw@strlen.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=info@metux.net \
    --cc=jeremy@azazel.net \
    --cc=kadlec@netfilter.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --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).