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

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

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 265 bytes --]

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

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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

[Eric W. Biederman]

Stephen Rothwell <sfr@canb.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

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

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 847 bytes --]

Hi Eric,

On Tue, 05 Feb 2019 15:29:04 -0600 ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> 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.

Ah, tricky.

> 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?

I can just get a copy of that tree and check for things in there as
well, I guess.  Though it shouldn't come up much (I hope :-))

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

Not that I am aware of and I guess it is as good as any.

Thanks.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 375 bytes --]

Hi all,

In commit

  e854a70f6f0b ("signal: Avoid corrupting si_pid and si_uid in do_notify_parent")

Fixes tag

  Fixes: 6588c1e3ff01 ("signals: SI_USER: Masquerade si_pid when crossing pid ns boundary

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]