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] [day] [month] [year] [list]
Message-ID: <CAHk-=wiB+Q+KbMBXtZZyMChdg8E8fBL8uipJn4j_rFxbAXangA@mail.gmail.com>
Date:   Thu, 16 Dec 2021 09:13:11 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     David Howells <dhowells@...hat.com>
Cc:     Marc Dionne <marc.dionne@...istor.com>,
        Jeffrey E Altman <jaltman@...istor.com>,
        linux-afs@...ts.infradead.org,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] afs: Fix mmap

On Tue, Dec 14, 2021 at 1:22 AM David Howells <dhowells@...hat.com> wrote:
>
> Could you apply this patch please?  Note the odd email address in the
> Reported-by and Tested-by fields.  That's an attempt to note Auristor's
> internal testcase ID for their tracking purposes.  Is this a reasonable way
> to do it?  It's kind of modelled on what syzbot does.

Yeah, this looks sane to me.

I don't like bare bug tracking IDs that don't tell anybody else
anything, but the "embedding it in the email" trick means that it now
(a) gives a contact for it so that it contains meaningful information
and (b) also acts a "namespace" for the testcase ID.

Applied.

            Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ