Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Kees Cook <keescook@chromium.org>
To:     luto@amacapital.net, kuniyu@amazon.com, wad@chromium.org
Cc:     Kees Cook <keescook@chromium.org>, linux-kernel@vger.kernel.org,
        ayudutta@amazon.com, brauner@kernel.org, kuni1840@gmail.com,
        syzbot+ab17848fe269b573eb71@syzkaller.appspotmail.com
Subject: Re: [PATCH v3] seccomp: Move copy_seccomp() to no failure path.
Date:   Mon, 29 Aug 2022 12:17:19 -0700
Message-Id: <166180063676.3312920.11804502368990110703.b4-ty@chromium.org>
In-Reply-To: <20220823154532.82913-1-kuniyu@amazon.com>
References: <20220823154532.82913-1-kuniyu@amazon.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 23 Aug 2022 08:45:32 -0700, Kuniyuki Iwashima wrote:
> Our syzbot instance reported memory leaks in do_seccomp() [0], similar
> to the report [1].  It shows that we miss freeing struct seccomp_filter
> and some objects included in it.
> 
> We can reproduce the issue with the program below [2] which calls one
> seccomp() and two clone() syscalls.
> 
> [...]

Applied to for-linus/seccomp, thanks!

[1/1] seccomp: Move copy_seccomp() to no failure path.
      https://git.kernel.org/kees/c/6d17452707ca

-- 
Kees Cook