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: <Y/79Tfn5kFIItUDD@sol.localdomain>
Date:   Tue, 28 Feb 2023 23:22:53 -0800
From:   Eric Biggers <ebiggers@...nel.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Slade Watkins <srw@...dewatkins.net>,
        Sasha Levin <sashal@...nel.org>,
        Amir Goldstein <amir73il@...il.com>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org
Subject: Re: AUTOSEL process

On Wed, Mar 01, 2023 at 07:09:49AM +0100, Greg KH wrote:
> 
> Why would the FAILED emails want to go to a mailing list?  If the people
> that were part of making the patch don't want to respond to a FAILED
> email, why would anyone on the mailing list?

The same reason we use mailing lists for kernel development at all instead of
just sending patches directly to the MAINTAINERS.

> 
> But hey, I'll be glad to take a change to my script to add that
> functionality if you want to make it, it's here:
> 	https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/scripts/bad_stable
> 

Ah, the classic "patches welcome".

Unfortunately, I don't think that can work very well for scripts that are only
ever used by at most two people -- you and Sasha.  Many even just by you,
apparently, as I see your name, email address, home directory, etc. hardcoded in
the scripts.  (BTW, where are the scripts Sasha uses for AUTOSEL?)

- Eric

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ