From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x225fK4IP0vQWrEXpKRnR0muX9kCU+PjavKjHnk8Sg8NTLONj/ttI88ufCELFdD8T/iAWlili ARC-Seal: i=1; a=rsa-sha256; t=1516908586; cv=none; d=google.com; s=arc-20160816; b=zzRm+LS4egmeOovRF7SH7yB2Q/QaG1FEkeO2kDawADJSARtBZWtmLh05di1JGCWoZ2 WSP6FsDmPdUYi9GsDKaRBE1tMf9jsWkTQC3tgDB2iGVLv/QpdJGHvVUUSfveiAHpCpyl td+QxL3F5zQiE91jSFCnTIAw+rEpqdDogbkDHynY1L3WNrL5ARRJeelxaoc5jxCupKYM 156uDDkxLUA+zP5kQeJGHVttve51UrSHP145uiYNzsXMy3SgJjd/04Ma7ayljnZ1/O1y 2J4mq24KvqLtNGu9O2gVl8XnEEy5fL45z56X/EcdfPFfF2beWAR9Goc9ohVJ60axpT1S 5GPA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=message-id:date:subject:cc:to:from:arc-authentication-results; bh=CsJgnvBoFXEG9ayT1Hg+OAPQoKjQiftE7z/v3RF18b8=; b=mNpS+B8k1Fx8zD5ewFoqgv50q7GXKxfXeL01sZJd24nq6Qm7x5R0YS2e3MX9FBbCPi EbFOnXylj8rkRKjCYHnsdtaWQbOetTr9nps4LY7ZEBzdYR/Vjyxuo6SgoLs2Y7LujHBV Mnr1w4ebFniYrI9CSsUDXitpW2/I7votEBukQvOhYX/qokIyn1thkLL2paJslB3nAuDu So+QlumbGOSZlQOqOBN9GbVUiiSmEiSjKWpD8bmgSwXYLJw/J4TgcCokhu6ah9wP4CJm 026fgF/smnJJB5q5k0sTVkISE6y3etX1qmRvsVMj63b/yMrXLnvfNhb7x5UXgjf1Xijz Z+lQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of hdegoede@redhat.com designates 209.132.183.28 as permitted sender) smtp.mailfrom=hdegoede@redhat.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Authentication-Results: mx.google.com; spf=pass (google.com: domain of hdegoede@redhat.com designates 209.132.183.28 as permitted sender) smtp.mailfrom=hdegoede@redhat.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com From: Hans de Goede To: Arnd Bergmann , Greg Kroah-Hartman , Michael Thayer , Alexander Viro Cc: Hans de Goede , Larry Finger , Christoph Hellwig , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: [PATCH v4 0/1] fs: Add VirtualBox guest shared folder (vboxsf) support Date: Thu, 25 Jan 2018 20:29:42 +0100 Message-Id: <20180125192943.29483-1-hdegoede@redhat.com> X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1590593894077922555?= X-GMAIL-MSGID: =?utf-8?q?1590593938224844677?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: Hi All, As mentioned in the v2 cover letter, now that the vboxguest driver which the vboxsf (guest shared folder) fs driver depends on is queued for merging into 4.16 in char-misc-next, all the dependencies for the vboxsf are in place. So now its time to work towards also getting vboxsf merged. This version addresses (AFAIK) all comments made in response to v2. Changes in v4: -Drop "name=..." mount option, instead use the dev_name argument to the mount syscall, to keep compatibility with existing fstab entries -Fix "nls=%" match_table_t entry to "nls=%s" Changes in v3: -Use text only mount options, instead of a custom data struct -Stop caching full path in inode data, if parents gets renamed it will change -Fixed negative dentries handling -Dropped the force_reread flag for dirs, not sure what it was actually for but it is no good, doing a re-read on unlink of a file will lead to another file being skipped if the caller has already iterated over the entry for the unlinked file. -Use file_inode(), file_dentry() and d_inode() helpers -Prefix any non object-private symbols with vboxsf_ so as to not pollute the global namespace when builtin -Add MAINTAINERS entry -Misc. cleanups Changes in v2: -Removed various unused wrapper functions -Don't use i_private, instead defined alloc_inode and destroy_inode methods and use container_of. -Drop obsolete comment referencing people to http://www.atnf.csiro.au/people/rgooch/linux/vfs.txt -move the single symlink op of from lnkops.c to file.c -Use SPDX license headers -Replace SHFLROOT / SHFLHANDLE defines with normal types -Removed unnecessary S_ISREG checks -Got rid of bounce_buffer in regops, instead add a "user" flag to vboxsf_read / vboxsf_write, re-using the existing __user address support in the vboxguest module -Make vboxsf_wrappers return regular linux errno values -Use i_size_write to update size on writing -Convert doxygen style comments to kerneldoc style comments Please review. Regards, Hans