linux-kernel - Re: linux-next: build warning after merge of the audit tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHC9VhRH-0FBuBoAxkY1azRtqBXzJ+ENJDnnwBNUYd7WsM-Xqg@mail.gmail.com>
Date:	Tue, 6 Oct 2015 13:23:19 -0400
From:	Paul Moore <paul@...l-moore.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the audit tree

On Tue, Oct 6, 2015 at 1:46 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Paul,
>
> After merging the audit tree, today's linux-next build (i386 defconfig
> and others) produced this warning:
>
> security/lsm_audit.c: In function 'dump_common_audit_data':
> security/lsm_audit.c:340:9: warning: passing argument 1 of 'unix_sk' discards 'const' qualifier from pointer target type
>      u = unix_sk(sk);
>          ^
> In file included from security/lsm_audit.c:22:0:
> include/net/af_unix.h:67:33: note: expected 'struct sock *' but argument is of type 'const struct sock *'
>  static inline struct unix_sock *unix_sk(struct sock *sk)
>                                  ^
>
> Introduced by commit
>
>   43cfd5e38587 ("audit: constify parts of common_audit_data and lsm_network_audit")

Hi Stephen,

I apologize for the build warning, for some reason it works just fine
in audit#next but causes problems on top of more current trees.  I'm
going to drop the patch until I've resolved the issue.

-- 
paul moore
www.paul-moore.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/