From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: dirty-pipe ?
Date: Wed, 9 Mar 2022 20:15:34 +0100 [thread overview]
Message-ID: <20220309201534.3a3b8e22@archlinux> (raw)
In-Reply-To: <CAJjrzcUo_30mZAuWVN4W2WK=WcoFC_55_Lq5y7YxdjD37US_YA@mail.gmail.com>
On Wed, 9 Mar 2022 19:22:15 +0100, Arve Barsnes wrote:
>On Wed, 9 Mar 2022 at 19:16, gene heskett <gheskett@shentel.net> wrote:
>> Is this kernel vulnerable?
>> 4.19.71-rt24-v7l+ #1 SMP PREEMPT RT Thu Feb 6 07:09:18 EST 2020
>> armv7l GNU/Linux
>
>No, the vulnerability was introduced in kernel 5.8
Hi,
that is my understanding, too, hence my reply yesterday on another
mailing list, see
https://lists.ubuntu.com/archives/ubuntu-users/2022-March/307093.html .
However, 4.19 kernels received many patches and I haven't verified
myself that non of those patches includes a backport introducing dirty
pipe or any other nasty issue.
Regards,
Ralf
--
[rocketmouse@archlinux ~]$ pacman -Q linux-rt{-cornflower,-pussytoes,,-securityink}|cut -d\ -f2
4.19.230_rt103-0.300
4.19.227_rt102-0.300
4.19.223_rt100-0.1000
4.19.219_rt97-0.300
[rocketmouse@archlinux ~]$ echo $(uname -srvm;zgrep CONFIG_AUDIT\ /proc/config.gz || zgrep CONFIG_AUDIT= /proc/config.gz);echo;cat /proc/cmdline;echo;grep . /sys/devices/system/cpu/vulnerabilities/* | cut -d/ -f7;rtirq status|head -8
Linux 4.19.230-rt103-0.300-cornflower #1 SMP PREEMPT RT Tue, 22 Feb 2022 07:30:23 +0100 x86_64 # CONFIG_AUDIT is not set
BOOT_IMAGE=../vmlinuz-linux-rt-cornflower root=LABEL=s3.archlinux ro initrd=../intel-ucode.img,../initramfs-linux-rt-cornflower.img
itlb_multihit:KVM: Mitigation: Split huge pages
l1tf:Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
mds:Mitigation: Clear CPU buffers; SMT disabled
meltdown:Mitigation: PTI
spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl and seccomp
spectre_v1:Mitigation: usercopy
spectre_v2:Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
srbds:Mitigation: Microcode
tsx_async_abort:Not affected
PID CLS RTPRIO NI PRI %CPU STAT COMMAND
142 FF 90 - 130 0.0 S irq/24-xhci_hcd
153 FF 90 - 130 0.0 S irq/16-ehci_hcd
156 FF 89 - 129 0.0 S irq/23-ehci_hcd
312 FF 85 - 125 0.0 S irq/16-snd_hdsp
339 FF 80 - 120 0.0 S irq/16-snd_ice1
42 FF 50 - 90 0.0 S irq/9-acpi
next prev parent reply other threads:[~2022-04-06 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:26 dirty-pipe ? gene heskett
2022-03-09 18:22 ` Arve Barsnes
2022-03-09 19:15 ` Ralf Mardorf [this message]
2022-03-14 18:02 ` Daniel Wagner
[not found] ` <1752976.GyQ78RL1t7@coyote>
2022-03-15 9:35 ` Daniel Wagner
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=20220309201534.3a3b8e22@archlinux \
--to=ralf.mardorf@alice-dsl.net \
--cc=linux-rt-users@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.