linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	"heming.zhao@suse.com" <heming.zhao@suse.com>
Cc: dcermak@suse.com
Subject: Re: [linux-lvm] [PATCH] gcc: change zero-sized array to fexlible array
Date: Wed, 2 Sep 2020 17:22:01 +0200	[thread overview]
Message-ID: <66fe8fdc-3147-8a22-9a34-7201f4187be4@redhat.com> (raw)
In-Reply-To: <4bb3e590-39f1-75e7-9000-03d1d3fc0e73@suse.com>

Dne 29. 08. 20 v 5:11 heming.zhao@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

  reply	other threads:[~2020-09-02 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 16:05 [linux-lvm] [PATCH] gcc: change zero-sized array to fexlible array Zhao Heming
2020-08-20 16:08 ` heming.zhao
2020-08-26  5:18 ` heming.zhao
2020-08-28 19:32   ` Zdenek Kabelac
2020-08-29  3:11     ` heming.zhao
2020-09-02 15:22       ` Zdenek Kabelac [this message]
2020-09-03 14:58         ` heming.zhao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=66fe8fdc-3147-8a22-9a34-7201f4187be4@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=dcermak@suse.com \
    --cc=heming.zhao@suse.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).