From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dmitry Safonov <dima@arista.com>
Cc: <linux-kernel@vger.kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Hillf Danton <hdanton@sina.com>, <netdev@vger.kernel.org>,
<syzbot+a7e701c8385bd8543074@syzkaller.appspotmail.com>,
<syzbot+c43831072e7df506a646@syzkaller.appspotmail.com>
Subject: Re: [PATCH 0/3] xfrm/compat: syzbot-found fixes
Date: Mon, 2 Nov 2020 09:21:23 +0100 [thread overview]
Message-ID: <20201102082123.GC8805@gauss3.secunet.de> (raw)
In-Reply-To: <20201030022600.724932-1-dima@arista.com>
On Fri, Oct 30, 2020 at 02:25:57AM +0000, Dmitry Safonov wrote:
> WARN_ON() for XFRMA_UNSPEC translation which likely no-one except
> syzkaller uses; properly zerofy tail-padding for 64-bit attribute;
> don't use __GFP_ZERO as the memory is initialized during translation.
>
> Cc: Steffen Klassert <steffen.klassert@secunet.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Hillf Danton <hdanton@sina.com>
> Cc: netdev@vger.kernel.org
>
> Thanks,
> Dmitry
>
> Dmitry Safonov (3):
> xfrm/compat: Translate by copying XFRMA_UNSPEC attribute
> xfrm/compat: memset(0) 64-bit padding at right place
> xfrm/compat: Don't allocate memory with __GFP_ZERO
Can you please add 'Fixes' tags to all the patches.
Thanks!
prev parent reply other threads:[~2020-11-02 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 2:25 [PATCH 0/3] xfrm/compat: syzbot-found fixes Dmitry Safonov
2020-10-30 2:25 ` [PATCH 1/3] xfrm/compat: Translate by copying XFRMA_UNSPEC attribute Dmitry Safonov
2020-10-30 2:25 ` [PATCH 2/3] xfrm/compat: memset(0) 64-bit padding at right place Dmitry Safonov
2020-10-30 2:26 ` [PATCH 3/3] xfrm/compat: Don't allocate memory with __GFP_ZERO Dmitry Safonov
2020-11-02 8:21 ` 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=20201102082123.GC8805@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=hdanton@sina.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+a7e701c8385bd8543074@syzkaller.appspotmail.com \
--cc=syzbot+c43831072e7df506a646@syzkaller.appspotmail.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