linux-kernel - [PATCH 0/3] overlayfs fixes for v3.8 and later base

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-next>] [day] [month] [year] [list]

Date:	Thu, 27 Jun 2013 17:26:41 +0100
From:	Andy Whitcroft <apw@...onical.com>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	Andy Whitcroft <apw@...onical.com>, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, mszeredi@...e.cz,
	Al Viro <viro@...iv.linux.org.uk>
Subject: [PATCH 0/3] overlayfs fixes for v3.8 and later base

Following this email are three patches against overlayfs.v17 which allow
it to work against v3.10-rc6 and later.  With these applied overlayfs
passes basic testing.

overlayfs -- ovl_path_open should not take path reference

    Found this in testing on Ubuntu raring, testing against loopback
    mounted files.  Without this change we were unable to release the
    loopback device for reuse.  Looking at it actually we were also leaking
    references on the root filesystem, but these are not as obvious.

vfs: export do_splice_direct() to modules -- fix
overlayfs -- follow change to do_splice_direct interface

    This pair switch us to the new do_splice_direct interface.  Note that
    the first one is effectivly a fix for the existing export of this
    interface and likely should be merged down into it.

Please consider for your overlayfs branch.

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