linux-kernel - Re: linux-next: build warning after merge of the vfs 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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Jul 2011 06:17:37 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Josef Bacik <josef@...hat.com>
Subject: Re: linux-next: build warning after merge of the vfs tree

On Mon, Jul 18, 2011 at 03:04:56PM +1000, Stephen Rothwell wrote:
> Hi Al,
> 
> After merging the vfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
> 
> drivers/char/ps3flash.c:347:2: warning: initialization from incompatible pointer type
> 
> Introduced by commit 62ec115d5b9c ("fs: push i_mutex and
> filemap_write_and_wait down into ->fsync() handlers").

Argh...  There had been several places where ->fsync() change hadn't been
done in the original patch; I've patched them up, but forgot to change the
prototype in this one ;-/

s/file,/& loff_t start, loff_t end,/ in the obvious place; I'll push the
updated variant in a few.
--
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/