linux-kernel - Re: [RFC Aufs2 #2 21/28] aufs sysfs entries

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:	Tue, 17 Mar 2009 21:56:11 +0900
From:	hooanon05@...oo.co.jp
To:	Evgeniy Polyakov <zbr@...emap.net>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [RFC Aufs2 #2 21/28] aufs sysfs entries 


Evgeniy Polyakov:
> On Tue, Mar 17, 2009 at 01:05:47PM +0900, hooanon05@...oo.co.jp (hooanon05@...oo.co.jp) wrote:
> > Is the limit of PATH_MAX applied to the absolute path too?
> 
> No, only path used in the given operation (related or absolute) is
> limited. If related path is converted into the absolute just for the
> purpose of dump and not to be used in some syscall, it can have any
> length, so you may need to rethink which pathes are presented in sysfs
> and what should be moved outside.

As a result, current code is implemented.
- aufs entries under sysfs print the absolute path.
- sets limit (PAGE_SIZE) to its length.
- and I think it is enough.

Theoretically, every entries under procfs (or sysfs?) which contains the
absolute path have this problem.


J. R. Okajima
--
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/