Re: [stable] seccomp: Move copy_seccomp() to no failure path.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From:   Daniel Borkmann <daniel@xxxxxxxxxxxxx>
Date:   Tue, 21 Mar 2023 23:26:09 +0100
> Hi Kuniyuki,
> 
> On 3/21/23 6:09 PM, Kuniyuki Iwashima wrote:
> [...]
> >> Link: https://github.com/awslabs/amazon-eks-ami/issues/1179
> >> Link: https://github.com/awslabs/amazon-eks-ami/issues/1219
> > 
> > I'm investigating these issues with EKS folks.  On the issue 1179, the
> > customer was using our 5.4 kernel, and on 1219, 5.10 kernel.
> > 
> > Then, I found my memleak fix commit a1140cb215fa ("seccomp: Move
> > copy_seccomp() to no failure path.") was not backported to upstream 5.10
> > stable trees.  We'll test if the issue can be reproduced with/without
> > the fix.
> 
> Good to know that 5.10 EKS kernel is based on top of stable one. It indeed
> looks like this could be happening there given a1140cb215fa is missing. I
> wonder given it has proper Fixes tag why it didn't made it into stable tree
> already. Thanks for checking, if it confirms, then lets ping Greg to cherry-
> pick.

The commit conflicted with 5.10, so it was missed, I guess.
I'll send a backporting patch for stable.

Thanks,
Kuniyuki



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux