public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: Micah Morton <mortonm@chromium.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kselftest@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jaswinder.singh@linaro.org, shuah <shuah@kernel.org>
Subject: Re: [BUGFIX PATCH v2 0/3] selftests: safesetid: Fix some bugs in safesetid test
Date: Thu, 5 Dec 2019 09:44:52 -0700	[thread overview]
Message-ID: <3bad79d5-eada-7e96-4210-c4888bfb710f@kernel.org> (raw)
In-Reply-To: <CAJ-EccNKk30b_wtvz=PUVmMVfF8YNagXMcy3Uhj53DzFbgmb6A@mail.gmail.com>

On 12/5/19 9:40 AM, Micah Morton wrote:
> On Thu, Dec 5, 2019 at 4:20 AM Masami Hiramatsu <mhiramat@kernel.org> wrote:
>>
>> Hi,
>>
>> Here is the v2 series to fix build warnings and erorrs on
>> kselftest safesetid.
>> This version includes a fix for a runtime error.
>>
>> Thank you,
>>
>> ---
>>
>> Masami Hiramatsu (3):
>>        selftests: safesetid: Move link library to LDLIBS
>>        selftests: safesetid: Check the return value of setuid/setgid
>>        selftests: safesetid: Fix Makefile to set correct test program
> 
> These 3 fixes look good, thanks. Were you thinking they would go
> through my SafeSetID tree or is there a dedicated one for selftests? I
> guess if you're not sure someone else on here can chime in, or I can
> just take them through my tree if I don't hear anything.
> 

Yes. There is a linux-kselftest tree dedicated to selftests.
I can take them.


>>
>>
>>   tools/testing/selftests/safesetid/Makefile         |    5 +++--
>>   tools/testing/selftests/safesetid/safesetid-test.c |   15 ++++++++++-----
>>   2 files changed, 13 insertions(+), 7 deletions(-)
>>
>> --

thanks,
-- Shuah


  reply	other threads:[~2019-12-05 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 12:20 [BUGFIX PATCH v2 0/3] selftests: safesetid: Fix some bugs in safesetid test Masami Hiramatsu
2019-12-05 12:20 ` [BUGFIX PATCH v2 1/3] selftests: safesetid: Move link library to LDLIBS Masami Hiramatsu
2019-12-05 12:21 ` [BUGFIX PATCH v2 2/3] selftests: safesetid: Check the return value of setuid/setgid Masami Hiramatsu
2019-12-05 12:21 ` [BUGFIX PATCH v2 3/3] selftests: safesetid: Fix Makefile to set correct test program Masami Hiramatsu
2019-12-05 16:40 ` [BUGFIX PATCH v2 0/3] selftests: safesetid: Fix some bugs in safesetid test Micah Morton
2019-12-05 16:44   ` shuah [this message]
2019-12-06  1:23     ` Masami Hiramatsu

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=3bad79d5-eada-7e96-4210-c4888bfb710f@kernel.org \
    --to=shuah@kernel.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mortonm@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox