From: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Sergey Muraviov <sergey(dot)k(dot)muraviov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: sepgsql: label regression test failed |
Date: | 2014-05-16 12:50:43 |
Message-ID: | CADyhKSWL12+myjbg_8itnwM5N9jT540WEnS00uNLHZTBH4ZXwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2014-05-16 16:26 GMT+09:00 Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>:
> On 05/14/2014 07:33 AM, Sergey Muraviov wrote:
>>
>> I've got this compiler warning:
>> relation.c: In function ‘sepgsql_relation_drop’:
>> relation.c:472:25: warning: ‘tclass’ may be used uninitialized in this
>> function [-Wmaybe-uninitialized]
>> sepgsql_avc_check_perms(&object,
>> ^
>
> KaiGei, could you take a look at this warning, too? It looks like a genuine
> bug to me, but I'm not sure what we should do there instead.
>
This warning is harmless, because the code path that does not initialize
"tclass" variable (a case when dropped relation is index) never goes to
the code path that references "tclass".
It just checks schema's {remove_name} permission, then jumps to
another code path for index, never backed.
BTW, I could not produce this message in my environment with -Wall.
(Fedora 20, gcc-4.8.2). Is it a newer compiler's wisdom?
Thanks,
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
Attachment | Content-Type | Size |
---|---|---|
sepgsql-fixup-maybe-uninitialized-warnning.patch | application/octet-stream | 687 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Jürgen Schönig | 2014-05-16 13:15:57 | Re: Priority table or Cache table |
Previous Message | Sameer Thakur | 2014-05-16 10:29:01 | Re: Priority table or Cache table |