From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH next] security: smack: fix sap undeclared error in smack_socket_sendmsg
Date: Fri, 10 May 2019 09:01:51 +0800 [thread overview]
Message-ID: <7da8fa41-39d1-ad79-44db-9ef352dca4be@huawei.com> (raw)
In-Reply-To: <73cebc57-3947-c438-9316-0c64302e97e5@schaufler-ca.com>
On 2019/5/9 23:29, Casey Schaufler wrote:
> On 5/9/2019 5:46 AM, Kefeng Wang wrote:
>> If CONFIG_IPV6 is disabled, there is build error, fix it.
>>
>> security/smack/smack_lsm.c: In function ‘smack_socket_sendmsg’:
>> security/smack/smack_lsm.c:3698:7: error: ‘sap’ undeclared (first use in this function)
>> sap->sin6_family != AF_INET6)
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>
> Thank you for your patch. This has already been fixed and
> will be in 5.2 when James sends the pull request.
ok ; )
>
>> ---
>> security/smack/smack_lsm.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
>> index b5b333d72637..ff5b7dc6816f 100644
>> --- a/security/smack/smack_lsm.c
>> +++ b/security/smack/smack_lsm.c
>> @@ -3693,6 +3693,7 @@ static int smack_socket_sendmsg(struct socket *sock, struct msghdr *msg,
>> return -EINVAL;
>> rc = smack_netlabel_send(sock->sk, sip);
>> break;
>> +#if IS_ENABLED(CONFIG_IPV6)
>> case AF_INET6:
>> if (msg->msg_namelen < SIN6_LEN_RFC2133 ||
>> sap->sin6_family != AF_INET6)
>> @@ -3707,6 +3708,7 @@ static int smack_socket_sendmsg(struct socket *sock, struct msghdr *msg,
>> rc = smk_ipv6_port_check(sock->sk, sap, SMK_SENDING);
>> #endif
>> break;
>> +#endif
>> }
>> return rc;
>> }
>
>
prev parent reply other threads:[~2019-05-10 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 12:46 [PATCH next] security: smack: fix sap undeclared error in smack_socket_sendmsg Kefeng Wang
2019-05-09 15:29 ` Casey Schaufler
2019-05-10 1:01 ` Kefeng Wang [this message]
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=7da8fa41-39d1-ad79-44db-9ef352dca4be@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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