linux-kernel - Re: [GIT PULL] llseek conversion

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: <201010221318.36457.arnd@arndb.de>
Date:	Fri, 22 Oct 2010 13:18:36 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] llseek conversion

On Friday 22 October 2010 13:11:53 Christoph Hellwig wrote:
> On Fri, Oct 22, 2010 at 01:10:08PM +0200, Arnd Bergmann wrote:
> > There are a few new drivers in linux-next that introduce additional
> > file_operations. These can all use no_llseek and I can follow up
> > with a patch to make that explicit when they get merged.
> 
> I don't think there's any reason to make that explicit.  In fact once
> your transition has settled we can just kill no_llseek.

Fair enough.

I thought about leaving out all no_llseek instances right away, but I
left them in because that allowed me to verify that my script actually
caught every single instance.

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