Hi Linus,
Please pull these Landlock updates for v5.18-rc1 . These two patches
have been successfully tested in the latest linux-next releases for
several weeks. They contain minor fixes:
* One addresses a memory leak in a user space sample. In practice, this
memory leak doesn't stay long because of the following execve call,
but let's fix it anyway.
* The second patch standardize the Landlock ruleset file descriptor name
with square brackets.
Regards,
Mickaël
--
The following changes since commit dcb85f85fa6f142aae1fe86f399d4503d49f2b60:
gcc-plugins/stackleak: Use noinstr in favor of notrace (2022-02-03 17:02:21 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-5.18-rc1
for you to fetch changes up to aea0b9f2486da8497f35c7114b764bf55e17c7ea:
landlock: Use square brackets around "landlock-ruleset" (2022-02-04 14:07:44 +0100)
----------------------------------------------------------------
Landlock updates for v5.18-rc1
These two commits contain a minor fix for the sandboxer sample, and a
Landlock ruleset FD name standardization.
----------------------------------------------------------------
Christian Brauner (1):
landlock: Use square brackets around "landlock-ruleset"
Tom Rix (1):
samples/landlock: Fix path_list memory leak
samples/landlock/sandboxer.c | 1 +
security/landlock/syscalls.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
On Mon, Mar 21, 2022 at 4:58 AM Mickaël Salaün <[email protected]> wrote:
>
> Please pull these Landlock updates for v5.18-rc1 .
Mickaël, both your pull requests (this and the 'trusted_for(2)' one)
were marked as spam for me.
The reason seems to be that you're using a SMTP host that doesn't
actually do modern anti-spam measures (no DKIM), and while it does do
SPF, gmail really dislikes it.
There doesn't seem anything in particular standing out in the email
itself, so I suspect your hosting provider (seems to be infomaniak.ch)
ends up either being in a block of IP addresses that is also being
used for spam, or it's just allowing a lot of spam itself.
Some people think that gmail is being way too restrictive about these
kinds of things, but since I hate spam with a passion, I end up siding
with rather strict spam measures.. Honestly, if an email provider
doesn't do DKIM in this day and age, it's not a very good email
provider imho.
Linus
On 21/03/2022 18:37, Linus Torvalds wrote:
> On Mon, Mar 21, 2022 at 4:58 AM Mickaël Salaün <[email protected]> wrote:
>>
>> Please pull these Landlock updates for v5.18-rc1 .
>
> Mickaël, both your pull requests (this and the 'trusted_for(2)' one)
> were marked as spam for me.
>
> The reason seems to be that you're using a SMTP host that doesn't
> actually do modern anti-spam measures (no DKIM), and while it does do
> SPF, gmail really dislikes it.
>
> There doesn't seem anything in particular standing out in the email
> itself, so I suspect your hosting provider (seems to be infomaniak.ch)
> ends up either being in a block of IP addresses that is also being
> used for spam, or it's just allowing a lot of spam itself.
>
> Some people think that gmail is being way too restrictive about these
> kinds of things, but since I hate spam with a passion, I end up siding
> with rather strict spam measures.. Honestly, if an email provider
> doesn't do DKIM in this day and age, it's not a very good email
> provider imho.
Thanks, it should be good now. Is there anything else you want me to do?
Regards,
Mickaël
The pull request you sent on Mon, 21 Mar 2022 12:59:13 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-5.18-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/29cbaa3e60dfe48e341a3a5ce1c2d8f3d9e9667c
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html