[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b1c5aaa-9d9a-e38e-42b4-bb0509eba4b5@digikod.net>
Date: Tue, 12 Apr 2022 15:48:57 +0200
From: Mickaël Salaün <mic@...ikod.net>
To: Konstantin Meskhidze <konstantin.meskhidze@...wei.com>
Cc: willemdebruijn.kernel@...il.com,
linux-security-module@...r.kernel.org, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org, yusongping@...wei.com,
artem.kuzin@...wei.com, anton.sirazetdinov@...wei.com
Subject: Re: [RFC PATCH v4 07/15] landlock: user space API network support
On 12/04/2022 13:21, Mickaël Salaün wrote:
>
> On 09/03/2022 14:44, Konstantin Meskhidze wrote:
[...]
>> @@ -184,7 +185,7 @@ SYSCALL_DEFINE3(landlock_create_ruleset,
>>
>> /* Checks content (and 32-bits cast). */
>> if ((ruleset_attr.handled_access_fs | LANDLOCK_MASK_ACCESS_FS) !=
>> - LANDLOCK_MASK_ACCESS_FS)
>> + LANDLOCK_MASK_ACCESS_FS)
>
> Don't add cosmetic changes. FYI, I'm relying on the way Vim does line
> cuts, which is mostly tabs. Please try to do the same.
Well, let's make it simple and avoid tacit rules. I'll update most of
the existing Landlock code and tests to be formatted with clang-format
(-i *.[ch]), and I'll update the landlock-wip branch so that you can
base your next patch series on it. There should be some exceptions that
need customization but we'll see that in the next series. Anyway, don't
worry too much, just make sure you don't have style-only changes in your
patches.
Powered by blists - more mailing lists