From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "Steve French" <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>,
"Pavel Shilovsky"
<piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/3] bug fixes and code cleanups for inaccessible root patch
Date: Fri, 29 Jul 2016 22:38:18 +0100 [thread overview]
Message-ID: <1469828301-9937-1-git-send-email-sprabhu@redhat.com> (raw)
The fix for unaccessible root with summary
"fs/cifs: make share unaccessible at root level mountable"
introduces a few bugs. This series of patches cleans up some parts of the code
and also fixes a couple of bugs seen in the patch.
Sachin Prabhu (3):
Fix memory leaks in cifs_do_mount()
Compare prepaths when comparing superblocks
Move check for prefix path to within cifs_get_root()
fs/cifs/cifsfs.c | 29 ++++++++++++-----------------
fs/cifs/cifsproto.h | 2 +-
fs/cifs/connect.c | 31 +++++++++++++++++++++++++++++--
3 files changed, 42 insertions(+), 20 deletions(-)
--
2.5.5
next reply other threads:[~2016-07-29 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 21:38 Sachin Prabhu [this message]
[not found] ` <1469828301-9937-1-git-send-email-sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-29 21:38 ` [PATCH 1/3] Fix memory leaks in cifs_do_mount() Sachin Prabhu
2016-07-29 21:38 ` [PATCH 2/3] Compare prepaths when comparing superblocks Sachin Prabhu
2016-07-29 21:38 ` [PATCH 3/3] Move check for prefix path to within cifs_get_root() Sachin Prabhu
2016-08-01 7:56 ` [PATCH 0/3] bug fixes and code cleanups for inaccessible root patch Aurélien Aptel
2016-08-03 13:25 ` Aurélien Aptel
2016-08-03 21:54 ` Steve French
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=1469828301-9937-1-git-send-email-sprabhu@redhat.com \
--to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=aaptel-IBi9RG/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=piastryyy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).