Hi
On Tue, Apr 23, 2024 at 09:20:08AM +0200, Bastian Blank wrote:
> On Tue, Apr 23, 2024 at 09:06:47AM +0200, Bastian Blank wrote:
> > On Tue, Apr 23, 2024 at 08:12:28AM +0200, bouv...@buxtehude.debian.org
> > wrote:
> > > FWIW, and following Jacob Rhoads' remark, we are also running CrowdStrike
On Tue, Apr 23, 2024 at 09:06:47AM +0200, Bastian Blank wrote:
> On Tue, Apr 23, 2024 at 08:12:28AM +0200, bouv...@buxtehude.debian.org wrote:
> > FWIW, and following Jacob Rhoads' remark, we are also running CrowdStrike
> > Falcon Sensor on all our machines, virtuals servers and laptops alike.
>
Control: reassign -1 src:linux
Control: severity -1 normal
Control: tags -1 moreinfo
On Mon, Apr 22, 2024 at 09:12:59AM +0200, bouv...@buxtehude.debian.org wrote:
> Something seems wrong in 6.1.0-20, but it is not immediately wrong: it waits
> until some sort of trigger. After that, rebooting
FWIW, and following Jacob Rhoads' remark, we are also running CrowdStrike
Falcon Sensor on all our machines, virtuals servers and laptops alike.
That would explain why I don't have the same problem at home.
--
Cédric Bouvier
System Engineer, IRU Geneva
+41-22-918 2927 (direct)
Seeing this same issue. In my case, it ended up being caused by Crowdstrike
Falcon Sensor combined with this specific kernel. Reverting the kernel or
upgrading Falcon (via Falcon upgrade policy) works around this issue, for
now.
I think I see that 6.1.87 has attempted to fix some BHI
Same problem here, but with a different call trace. The RIP logline had
one of `security_file_permission` and `security_netlink_send`, I don't
remember which one.
6 matches
Mail list logo