linux-kernel - Re: [RFC] readdir mess

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]

Message-ID: <87proe81c1.fsf@devron.myhome.or.jp>
Date:	Wed, 13 Aug 2008 04:45:02 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Al Viro <viro@...IV.linux.org.uk>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] readdir mess

Linus Torvalds <torvalds@...ux-foundation.org> writes:

> As to -EOVERFLOW, I suspect we are better off just dropping that whole 
> logic. Returning -EOVERFLOW and truncating the readdir listing is likely 
> much worse than the alternative. It made sense back when we needed to get 
> people to upgrade the system interfaces, now it just means that old 
> binaries won't work at all.

However, there are some similar stuff: ->st_size, ->st_nlink and
->st_ino in stat() (cp_old_stat()). Maybe EOVERFLOW is the reason for
consistency...
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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/