linux-kernel - Re: linux-next: build warning after merge of the final tree (Linus' tree related)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1368112975-65m57crd-mutt-n-horiguchi@ah.jp.nec.com>
Date:	Thu, 09 May 2013 11:22:55 -0400
From:	Naoya Horiguchi <n-horiguchi@...jp.nec.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warning after merge of the final tree (Linus'
 tree related)

On Thu, May 09, 2013 at 01:55:04PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the final tree, today's linux-next build (arm defconfig)
> produced this warning:
> 
> ipc/shm.c: In function 'newseg':
> ipc/shm.c:494:18: warning: unused variable 'hs' [-Wunused-variable]
> 
> Introduced by commit af73e4d9506d ("hugetlbfs: fix mmap failure in
> unaligned size request") in Linus' tree.
> 
> Did the "[akpm@...ux-foundation.org: fix warning when
> CONFIG_HUGETLB_PAGE=n]" part get dropped?  Or was that something else?

In my original post, 2 auto variables hs were used both in newseg() and
sys_mmap_pgoff(), and Andrew fixed only one in sys_mmap_pgoff().
hs remains in newseg(), so it fires warning in linux-next.
Hours ago Li suggested another fix of af73e4d9506d and it implicitly
fixes this warning.
http://marc.info/?l=linux-kernel&m=136808335431220&w=2

Thanks,
Naoya
--
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/