From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 0/2] Fix misaligned ovl_fh
Date: Fri, 15 Nov 2019 13:33:02 +0200 [thread overview]
Message-ID: <20191115113304.16209-1-amir73il@gmail.com> (raw)
Miklos,
Beyond the regular tests, this has also been tortured
with my ovl-nested patches and tests.
Those have been very useful in flushing out nfs export bugs in the past
and they have also flushed out a few bugs from the RFC patch I sent
yesterday.
Thanks,
Amir.
Changes since RFC:
- Fix bug in ovl_verify_index()
- Open code ovl_dentry_to_fh() [Al]
- Zero buffer in ovl_encode_real_fh() [Al]
- Support decoding old (misaligned) file handles from the wire [Al]
- Add patch to simplify memory allocation in ovl_encode_real_fh() [Al]
Amir Goldstein (2):
ovl: make sure that real fid is 32bit aligned in memory
ovl: don't use a temp buf for encoding real fh
fs/overlayfs/copy_up.c | 53 +++++++++++++-------------
fs/overlayfs/export.c | 80 ++++++++++++++++++++++++----------------
fs/overlayfs/namei.c | 44 +++++++++++-----------
fs/overlayfs/overlayfs.h | 34 ++++++++++++++---
4 files changed, 124 insertions(+), 87 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-15 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 11:33 Amir Goldstein [this message]
2019-11-15 11:33 ` [PATCH v2 1/2] ovl: make sure that real fid is 32bit aligned in memory Amir Goldstein
2019-11-15 11:33 ` [PATCH v2 2/2] ovl: don't use a temp buf for encoding real fh Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191115113304.16209-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox