linux-kernel - Re: [PATCH] platform:x86 decouple telemetry driver from the optional IPC resources

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

Message-ID: <CAHp75VdTYajOmA09icFF5x6d-Qib_XjNFgM_vTzh8+mhEahb2g@mail.gmail.com>
Date:	Fri, 22 Apr 2016 00:13:56 +0300
From:	Andy Shevchenko <andy.shevchenko@...il.com>
To:	Darren Hart <dvhart@...radead.org>
Cc:	"Li, Aubrey" <aubrey.li@...ux.intel.com>, qipeng.zha@...el.com,
	platform-driver-x86@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] platform:x86 decouple telemetry driver from the optional
 IPC resources

On Fri, Apr 15, 2016 at 8:05 AM, Darren Hart <dvhart@...radead.org> wrote:

>> >>>> +       /*
>> >>>> +        * The following resources are optional
>> >>>> +        * - ISPDRIVER_IPC BASE_DATA
>> >>>> +        * - ISPDRIVER_IPC BASE_IFACE
>> >>>> +        * - GTDRIVER_IPC BASE_DATA
>> >>>> +        * - GTDRIVER_IPC BASE_IFACE
>> >>>> +        */
>> >>>>         res = platform_get_resource(pdev, IORESOURCE_MEM, 2);
>> >>>> -       addr = devm_ioremap_resource(&pdev->dev, res);
>> >>>> -       if (IS_ERR(addr))
>> >>>> -               return PTR_ERR(addr);
>> >>>> -       punit_ipcdev->base[ISPDRIVER_IPC][BASE_DATA] = addr;
>> >>>> +       if (res) {
>> >>>> +               addr = devm_ioremap_resource(&pdev->dev, res);
>> >>>> +               if (!IS_ERR(addr))
>> >>>> +                       punit_ipcdev->base[ISPDRIVER_IPC][BASE_DATA] = addr;
>> >>>> +       }
>> >>>
>> >>> And here, what about just replacing return to dev_warn()?
>> >>
>> >> I don't think we need to continue the subsequent ops if an error address
>> >> returns.
>> >
>> > Why is that? Will the driver fail to provide any functionality? Or could it be
>> > the other IFACEs could still be of some use?
>> >
>> > This one does need a justification.
>> >
>> We discussed this.
>> - For the necessary resources, if we obtain an error address, we should
>> return immediately.
>> - For the optional resources, we keep quiet if we don't get them, that
>> is, not throwing a warning out.
>
> Andy, he's checking for "res" now too, which is a good extra check since
> devm_ioremap_resource will issue a dev_err "invalid resource" if it's NULL, even
> though in our case, that's expected for an optional resource. This adds the
> extra nesting, and a dev_warn wouldn't be appropriate for an option resource.
>
> I'm happy to queue this to fixes at this point. Andy, are you OK with the
> resolution here?

Gmail hided this mail from me by some reason. I'm fine with the resolution.

-- 
With Best Regards,
Andy Shevchenko