All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/exec: Add binfmt_script regression test
Date: Mon, 15 Jun 2020 11:29:30 -0700	[thread overview]
Message-ID: <202006151128.EFFD6A6@keescook> (raw)
In-Reply-To: <159223571468.30953.4003723352312620963.git-patchwork-notify@kernel.org>

On Mon, Jun 15, 2020 at 03:41:54PM +0000, patchwork-bot+linux-kselftest@kernel.org wrote:
> Hello:
> 
> This patch was applied to shuah/linux-kselftest.git (refs/heads/next).

Hi! Thanks for snagging this, however, see below...

> 
> On Wed, 20 May 2020 02:05:56 -0700 you wrote:
> > While working on commit b5372fe5dc84 ("exec: load_script: Do not exec
> > truncated interpreter path"), I wrote a series of test scripts to verify
> > corner cases. However, soon after, commit 6eb3c3d0a52d ("exec: increase
> > BINPRM_BUF_SIZE to 256") landed, resulting in the tests needing to be
> > refactored for the larger BINPRM_BUF_SIZE, which got lost on my TODO
> > list. During the recent exec refactoring work[1], the need for these tests
> > resurfaced, so I've finished them up for addition to the kernel selftests.
> > 
> > [...]
> 
> 
> Here is a summary with links:
>   - selftests/exec: Add binfmt_script regression test
>     https://git.kernel.org/shuah/linux-kselftest/c/b081320f0693cce0394f7c8bad9fba0b25982186
> 
> You are awesome, thank you!

This was already picked up by Eric for this execve series, and has
already landed in Linus's tree as b081320f0693cce0394f7c8bad9fba0b25982186

-- 
Kees Cook

      parent reply	other threads:[~2020-06-15 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20  9:05 [PATCH] selftests/exec: Add binfmt_script regression test Kees Cook
2020-05-20 22:01 ` Eric W. Biederman
     [not found] ` <159223571468.30953.4003723352312620963.git-patchwork-notify@kernel.org>
2020-06-15 18:29   ` Kees Cook [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=202006151128.EFFD6A6@keescook \
    --to=keescook@chromium.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=skhan@linuxfoundation.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.