lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPnZJGCcsSoJVs_ct_9ngTrPpH0dxAakJCVGnYaYCDPbw2EyLQ@mail.gmail.com>
Date: Mon, 1 Jan 2024 04:15:33 +0300
From: Askar Safin <safinaskar@...il.com>
To: Stefan Berger <stefanb@...ux.ibm.com>
Cc: Rob Landley <rob@...dley.net>, gregkh@...uxfoundation.org, initramfs@...r.kernel.org, 
	linux-kernel@...r.kernel.org, stable@...r.kernel.org, zohar@...ux.ibm.com
Subject: Re: [PATCH v3] rootfs: Fix support for rootfstype= when root= is given

Hi, Stefan. Hi, Rob.

> My intention is to be able to pass rootfstype= to the kernel and have it
> interpreted correctly in the presence of root=, which currently does not
> work
Stefan, let me repeat: your patch, which does exactly this, got to
linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=21528c69a0d8483f7c6345b1a0bc8d8975e9a172

I think there is some misunderstanding here. First, there is Stefan's
patch (based on Rob's patch), which makes the kernel parse rootfstype=
even if root= is present. As well as I understand, we all agree that
this patch is needed, and it was applied to linux-next, so all is
good!

Second, there was my suggestion to introduce rdrootfstype= option. You
both reacted sceptically, so I withdraw this suggestion

-- 
Askar Safin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ