[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: xen-analysis ECLAIR support
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Luca Fancellu <Luca.Fancellu@xxxxxxx>
- Date: Mon, 4 Sep 2023 12:14:22 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=+RnS05jI6H3JpjPV5IefLl8NNzXrmBZZ1KhpgGvGT2k=; b=PoD2u3IwgGivQdRW0/keBBqmQ6UQ2VCaDMscHMFrC8uKeMcxWZHRzP1FqHxzr27DBMxR/sEmZXebjxSDIzhxcrfuSFAz2kO3qBVH8fnVAhdsxs1tehZyEPv2dOC7Me/Yi/JcgHFbSQhgn9qzJIy8wGdZJrhxFzTBcguCIqUmXKoD9BHBR2GMh7ciex3muiVpDnLC3YWRPHxxtD+6ny5oKvCkg300vJURv4/CikV9cb8DIDur0qXDDy8SKpfmjm1HehwrBpqcla8svBGnwhMnuIksLxUDeJsJ/NcQux79JydCfkC29dxrJDItq0nrbgpAHMvj0O0kl+TC95cRmamFCw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b+4mrTqPSJg9Xc2ykNqsSOaupkTEDbZlKP8xnNfN8y+cSo9Lv1m1zZZzCtw+Gxl0gKycv9EGPZnyaoJsOPoAZwKSq2jS7nHRkQpEa7G6z0fJNGqj4WOzR0fLhg1qHUgXHPt6dn6p4iWfN9PmYSScBNG8DaC4+4c6ZXRn4HnfdAu8SutRGZr3aPOIzLdk0vZY0+B77pSIxsa/sEy92NTS3sFMwO7AHEcW+J1WPMW4gAab0RPXBqy+eDUtGAU5k/cuRgBxrZn+z2Hzdiq/Wk6DJaV2GR+t7w0axvJ5lqkxMuHV5DpY8FdB2nvtwYnrCIRU+dL47GXP8CD8GFEWLLBHDQ==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Cc: Michal Orzel <michal.orzel@xxxxxxx>, Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>
- Delivery-date: Mon, 04 Sep 2023 12:17:20 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Thread-index: AQHZ1tnZvpm8hZMDREGKKcjBarux3K/6q84AgAACt4CAD/ZmgA==
- Thread-topic: xen-analysis ECLAIR support
> On 25 Aug 2023, at 09:28, Jan Beulich <jbeulich@xxxxxxxx> wrote:
>
> On 25.08.2023 10:18, Michal Orzel wrote:
>> Hi Stefano,
>>
>> On 25/08/2023 00:24, Stefano Stabellini wrote:
>>>
>>>
>>> Hi Luca,
>>>
>>> We are looking into adding ECLAIR support for xen-analysis so that we
>>> can use the SAF-n-safe tags also with ECLAIR.
>>>
>>> One question that came up is about multi-line statements. For instance,
>>> in a case like the following:
>>>
>>> diff --git a/xen/common/inflate.c b/xen/common/inflate.c
>>> index 8fa4b96d12..8bdc9208da 100644
>>> --- a/xen/common/inflate.c
>>> +++ b/xen/common/inflate.c
>>> @@ -1201,6 +1201,7 @@ static int __init gunzip(void)
>>> magic[1] = NEXTBYTE();
>>> method = NEXTBYTE();
>>>
>>> + /* SAF-1-safe */
>>> if (magic[0] != 037 ||
>>> ((magic[1] != 0213) && (magic[1] != 0236))) {
>>> error("bad gzip magic numbers");
>>>
>>>
>>> Would SAF-1-safe cover both 037, and also 0213 and 0213?
>>> Or would it cover only 037?
>>>
>>> We haven't use SAFE-n-safe extensively through the codebase yet but
>>> my understanding is that SAFE-n-safe would cover the entire statement of
>>> the following line, even if it is multi-line. Is that also your
>>> understanding? Does it work like that with cppcheck?
>> Looking at the docs and the actual script, only the single line below SAF
>> comment is excluded.
>> So in your case you would require:
>>
>> /* SAF-1-safe */
>> if (magic[0] != 037 ||
>> /* SAF-1-safe */
>> ((magic[1] != 0213) && (magic[1] != 0236))) {
>> error("bad gzip magic numbers");
>
> Or (perhaps more neatly):
>
> /* SAF-1-safe */
> if (magic[0] != 037 || (magic[1] != 0213 && magic[1] != 0236)) {
> error("bad gzip magic numbers");
+1 for this approach, I was going to suggest it
>
> Jan
|