linux-kernel - Re: [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain

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>] [day] [month] [year] [list]

Message-ID: <20170525082215.4736027d@xeon-e3>
Date:   Thu, 25 May 2017 08:52:08 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Alan Cox <gnomes@...rguk.ukuu.org.uk>
Cc:     Haiyang Zhang <haiyangz@...rosoft.com>,
        "olaf@...fle.de" <olaf@...fle.de>, linux-pci@...r.kernel.org,
        driverdev-devel@...uxdriverproject.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain

On Thu, 25 May 2017 14:19:55 +0100
Alan Cox <gnomes@...rguk.ukuu.org.uk> wrote:

> > > Signed-off-by: Haiyang Zhang <haiyangz@...rosoft.com>
> > > ---    
> > 
> > According to Stephen Hemminger <sthemmin@...rosoft.com>, there are
> > additional programs, like X.org, DPDK, are also using 16-bit only
> > PCI domain numbers. So, I'm submitting this patch for re-consideration.  
> 
> The correct way to handle this is to send the needed patches to DPDK and
> to X.org both of whom will I am sure be delighted to get it fixed in
> their codebase.

Both projects have stable ABI requirements. And the lead time to get
the change propagated out to applications is long (>5yrs) even longer
with the Enterprise distro's. As developers we can all just pass the
buck but this doesn't help users in any reasonable time fram. It is not
as simple as just making a patch or pull request for their upstream
code bases.