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: <20210110101929.GG4035784@sasha-vm>
Date:   Sun, 10 Jan 2021 05:19:29 -0500
From:   Sasha Levin <sashal@...nel.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Sedat Dilek <sedat.dilek@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        stable@...r.kernel.org
Subject: Re: depmod fixes for linux-stable releases

On Sat, Jan 09, 2021 at 05:23:22PM -0800, Linus Torvalds wrote:
>Ack, I think 436e980e2ed5 ("kbuild: don't hardcode depmod path") is
>stable material even if it doesn't fix a bug.
>
>Not only does the fix for that commit not make sense without the
>commit in the first place, but any environment that sets depmod
>somewhere else might well be an environment that still wants stable
>kernels.
>
>It may not be the traditional case, but there's little reason for the
>kernel build to force that /sbin/depmod location.

I'll take it, thanks!

-- 
Thanks,
Sasha

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ