linux-kernel - Re: linux-next: Fixes tag needs some work in the userns tree

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]

Date:   Tue, 05 Feb 2019 15:29:04 -0600
From:   ebiederm@...ssion.com (Eric W. Biederman)
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the userns tree

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> Hi Eric,
>
> In commit
>
>   a692933a8769 ("signal: Always attempt to allocate siginfo for SIGSTOP")
>
> Fixes tag
>
>   Fixes: 6dfc88977e42 ("[PATCH] shared thread signals")
>
> has these problem(s):
>
>   - Target SHA1 does not exist

The SHA1 tag does exist and I have another tag:
History Tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
That lists the tree it actually came from.

That is the best way I can see to handle bugs that predate v2.6.12 that
Linus first put into git.

Would it make sense to graft you tree that you check for the existence
of bad sha1s to Thomas's import of the bk tree into git?

Is there a better way to refer to old commits that I haven't seen?

Eric