[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e83d9e6f-738f-a4b0-f556-8b162c5bd65d@huawei.com>
Date: Tue, 24 May 2022 11:55:41 +0300
From: Konstantin Meskhidze <konstantin.meskhidze@...wei.com>
To: Mickaël Salaün <mic@...ikod.net>
CC: <willemdebruijn.kernel@...il.com>,
<linux-security-module@...r.kernel.org>, <netdev@...r.kernel.org>,
<netfilter-devel@...r.kernel.org>, <yusongping@...wei.com>,
<anton.sirazetdinov@...wei.com>
Subject: Re: [PATCH v5 12/15] seltests/landlock: rules overlapping test
5/19/2022 6:04 PM, Mickaël Salaün пишет:
>
>
> On 19/05/2022 14:24, Konstantin Meskhidze wrote:
>>
>>
>> 5/16/2022 8:41 PM, Mickaël Salaün пишет:
>
> [...]
>
>>>> +
>>>> + /* Makes connection to socket with port[0] */
>>>> + ASSERT_EQ(0, connect(sockfd, (struct sockaddr *)&self->addr4[0],
>>>
>>> Can you please get rid of this (struct sockaddr *) type casting
>>> please (without compiler warning)?
>>>
>> Do you have a warning here? Cause I don't.
>
> There is no warning but this kind of cast is useless.
But addr4 is struct sockaddr_in type and connect/bind use struct
sockaddr type. That's why casting is needed here.
> .
Powered by blists - more mailing lists