[linux-lvm] [PATCH] gcc: change zero-sized array to fexlible array

[heming.zhao at suse.com]

Hello Zdenek,

For dependency, I patched below 3 patches, the opensuse tumbleweed building completed successfully

```
>From fd96f1014b11d073d775ea4777f3b3ba2eb93520 Mon Sep 17 00:00:00 2001
From: Zdenek Kabelac <zkabelac at redhat.com>
Date: Fri, 28 Aug 2020 19:15:01 +0200
Subject: [PATCH] gcc: zero-sized array to fexlible array C99


>From cc2218b4014015bd2633454e683293851183e08c Mon Sep 17 00:00:00 2001
From: Zhao Heming <heming.zhao at suse.com>
Date: Fri, 21 Aug 2020 00:05:04 +0800
Subject: [PATCH] gcc: change zero-sized array to fexlible array


>From b918afb693a62938e8189a5d07b13df8007ae062 Mon Sep 17 00:00:00 2001
From: Zdenek Kabelac <zkabelac at redhat.com>
Date: Fri, 28 Aug 2020 19:15:42 +0200                                                                     
Subject: [PATCH] tools: move struct element before variable lenght lis
```

Thanks,

On 9/2/20 11:22 PM, Zdenek Kabelac wrote:
> Dne 29. 08. 20 v 5:11 heming.zhao at suse.com napsal(a):
>>
>> These 3 zero-sized array blocked me to create lvm2 package for opensuse tumbleweed.
>> Opensuse uses OBS (open build service: https://openbuildservice.org/) to create rpm packages.
>> In my eyes, the OBS is black-box, it only showed these 3 warning and stopped building work.
>> So I filed patch only about these 3 places.
>>
>> the build error just related with [-Wstringop-overflow=]
>> ```
>> [   72s] In function 'strcpy',
>> [   72s]     inlined from '_store_str' at device_mapper/libdm-common.c:1453:2,
>> [   72s]     inlined from '_stack_node_op' at device_mapper/libdm-common.c:1589:2:
>> [   72s] /usr/include/bits/string_fortified.h:90:10: warning: '__builtin_strcpy' writing 1 or more bytes into a region of size 0 overflows the destination [-Wstringop-overflow=]
>> [   72s]    90 |   return __builtin___strcpy_chk (__dest, __src, __bos (__dest));
>> ```
>>
> 
> 
> Hi
> 
> So patches have've been pushed into master HEAD - so maybe you can try to validate whether this changes things for your builder server - we can then consider backporting to stable-2.0 branch.
> 
> Regards
> 
> Zdenek
>