linux-kernel - RE: linux-next: Signed-off-by missing for commit in the pci 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:   Mon, 9 Sep 2019 23:10:06 +0000
From:   Haiyang Zhang <haiyangz@...rosoft.com>
To:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
CC:     Bjorn Helgaas <bhelgaas@...gle.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sasha Levin <sashal@...nel.org>
Subject: RE: linux-next: Signed-off-by missing for commit in the pci tree



> -----Original Message-----
> From: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
> Sent: Wednesday, August 21, 2019 5:03 AM
> To: Stephen Rothwell <sfr@...b.auug.org.au>
> Cc: Bjorn Helgaas <bhelgaas@...gle.com>; Linux Next Mailing List <linux-
> next@...r.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@...r.kernel.org>; Sasha Levin <sashal@...nel.org>; Haiyang Zhang
> <haiyangz@...rosoft.com>
> Subject: Re: linux-next: Signed-off-by missing for commit in the pci tree
> 
> On Wed, Aug 21, 2019 at 07:19:39AM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Commit
> >
> >   c4a29fbba415 ("PCI: hv: Use bytes 4 and 5 from instance ID as the PCI
> domain numbers")
> >
> > is missing a Signed-off-by from its committer.
> >
> > Also, all the tags should be kept together, please.
> 
> Fixed it up in my pci/hv branch, apologies.
> 
> Lorenzo

Hi thanks for fixing this, but I found the following commit now has the Subject line
and commit message same as a previous patch.

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers?id=87b20a08dcc265959f5c59f18603ea0487fe609b

The correct message for the patch should be the msg below. Any possibility to 
fix it again?  Thanks.
- Haiyang

Subject:  PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain numbers

As recommended by Azure host team, the bytes 4, 5 have more uniqueness
(info entropy) than bytes 8, 9. So now we use bytes 4, 5 as the PCI domain
numbers. On older hosts, bytes 4, 5 can also be used -- no backward
compatibility issues here. The chance of collision is greatly reduced.

In the rare cases of collision, the driver code detects and finds another
number that is not in use.

Suggested-by: Michael Kelley <mikelley@...rosoft.com>
Signed-off-by: Haiyang Zhang <haiyangz@...rosoft.com>
Acked-by: Sasha Levin <sashal@...nel.org>
Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@....com>