linux-kernel - [RESENT][TRIVIAL][PATCH] SELinux: Use %lu for inode->i

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-next>] [day] [month] [year] [list]

Date:	Mon, 11 Jun 2007 12:29:45 +0200
From:	Tobias Oed <tobias.oed@...ant-fr.com>
To:	jmorris@...ei.org
CC:	tobias.oed@...ant-fr.com, sds@...ho.nsa.gov, trivial@...nel.org,
	linux-kernel@...r.kernel.org
Subject: [RESENT][TRIVIAL][PATCH] SELinux: Use %lu for inode->i_no when printing
 avcs

Resending this to a wider audience since the first attempt was mangled
and I haven't heard anything in a week.

Inode numbers are unsigned long and so need to %lu as format string of
printf. I have no idea why the __attribute__((format,..)) of 
audit_log_format
doesn't give us a warning.
Compile tested only.

Signed-off-by: Tobias Oed <tobias.oed@...ant-fr.com>

--- linux-2.6.21.3/security/selinux/avc.c.orig  2007-06-11
12:19:28.000000000 +0200
+++ linux-2.6.21.3/security/selinux/avc.c       2007-06-04
21:19:22.000000000 +0200
@@ -584,7 +584,7 @@ void avc_audit(u32 ssid, u32 tsid,
                                }
                        }
                        if (inode)
-                               audit_log_format(ab, " dev=%s ino=%ld",
+                               audit_log_format(ab, " dev=%s ino=%lu",
                                                 inode->i_sb->s_id,
                                                 inode->i_ino);
                        break;

-
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/