From: "Mickaël Salaün" <mic@digikod.net>
To: shuah@kernel.org, linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@amacapital.net>,
Kees Cook <keescook@chromium.org>, Will Drewry <wad@chromium.org>,
linux-kselftest@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed
Date: Thu, 7 Sep 2017 00:44:06 +0200 [thread overview]
Message-ID: <f5bbaf5a-30dc-5806-556a-8d161bcde3de@digikod.net> (raw)
In-Reply-To: <165e7361-d007-b1b4-116a-512ef074b6e4@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]
On 06/09/2017 03:26, Shuah Khan wrote:
> On 09/05/2017 02:38 PM, Mickaël Salaün wrote:
>>
>>
>> On 28/08/2017 18:42, Shuah Khan wrote:
>>> On 08/06/2017 05:23 PM, Mickaël Salaün wrote:
>>>> When a test process is not able to write to TH_LOG_STREAM, this step
>>>> mechanism enable to print the assert number which triggered the failure.
>>>> This can be enabled by setting _metadata->no_print to true at the
>>>> beginning of the test sequence.
>>>>
>>>> Update the seccomp-bpf test to return 0 if a test succeeded.
>>>>
>>>> This feature is needed for the Landlock tests.
>>>>
>>>> Signed-off-by: Mickaël Salaün <mic@digikod.net>
>>>> Cc: Andy Lutomirski <luto@amacapital.net>
>>>> Cc: Kees Cook <keescook@chromium.org>
>>>> Cc: Shuah Khan <shuah@kernel.org>
>>>> Cc: Will Drewry <wad@chromium.org>
>>>> Link: https://lkml.kernel.org/r/CAGXu5j+D-FP8Kt9unNOqKrQJP4DYTpmgkJxWykZyrYiVPz3Y3Q@mail.gmail.com
>>>
>>> I am looking through my Inbox and found this one. Okay to pull
>>> this in for 4.14-rc1?
>>
>> Yes, could you please pull this one instead of the one from my Landlock
>> patch series [1] (which is already in your tree)? This patch is more
>> up-to-date and include documentation.
>>
>
> Now this patch is in linux-kselftest next for 4.14-rc1 instead of
> the one from your landlock series. Please take a look and see if
> I git it right.
Yes, it is right. Thanks!
Mickaël
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-09-06 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 23:23 [PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed Mickaël Salaün
2017-08-28 16:42 ` Shuah Khan
2017-09-05 20:38 ` Mickaël Salaün
2017-09-06 1:26 ` Shuah Khan
2017-09-06 22:44 ` Mickaël Salaün [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=f5bbaf5a-30dc-5806-556a-8d161bcde3de@digikod.net \
--to=mic@digikod.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=wad@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;
as well as URLs for NNTP newsgroup(s).