linux-kernel - Re: [PATCH RESEND v2 2/7] PCI: Add pcie_reset_flr to follow calling convention of other reset methods

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 25 May 2021 17:17:25 +0200
From:   Krzysztof Wilczyński <kw@...ux.com>
To:     Amey Narkhede <ameynarkhede03@...il.com>
Cc:     Bjorn Helgaas <bhelgaas@...gle.com>, alex.williamson@...hat.com,
        raphael.norwitz@...anix.com, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v2 2/7] PCI: Add pcie_reset_flr to follow calling
 convention of other reset methods

Hi Amey,

Sorry for late reply!

[...]
> > Similarly to my suggestion in the first patch in the series, perhaps
> > using a boolean here would be an option.
> >
> > Having said that, the following existing functions aren't doing it, so
> > for the sake of keeping things consistent it might not be the best
> > option, as per:
> >
> >  static int pci_af_flr(struct pci_dev *dev, int probe)
> >  int nvme_disable_and_flr(struct pci_dev *dev, int probe)
> >
> > Krzysztof
>
> All the functions which implement different types of resets including
> quirks have ...reset(struct pci_dev *dev, int probe) signature.
> Should I modify all of them?

Might not be worth it to change anything then, especially if the other
functions there already use an integer argument to enable or disable the
problem or something else.  At least no in this series.

	Krzysztof