From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-fsdevel <linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: shrinking set of cifs fixes to merge for 2.6.39 to small set
Date: Mon, 11 Apr 2011 20:33:42 -0500 [thread overview]
Message-ID: <BANLkTi=72h+nv9BfB+1e69tW4Hb_u5U_TA@mail.gmail.com> (raw)
Since it is already past the merge window (was waiting to discuss some
fixes with others at the fs summit last week before merge), I shrunk
the list of cifs patches waiting for merge (in cifs-2.6.git) to a much
smaller set of more critical ones. See below. (I moved the others
temporarily to a for-2.6.40 branch in cifs-2.6.git). We (Jeff,
Shirish, I etc.) need to build/test more with this set before sending
though.
Jeff Layton (8):
cifs: check for private_data before trying to put it
cifs: replace /proc/fs/cifs/Experimental with a module parm
cifs: always do is_path_accessible check in cifs_mount
cifs: fix broken BCC check in is_valid_oplock_break
cifs: set ra_pages in backing_dev_info
cifs: clean up length checks in check2ndT2
cifs: clean up various nits in unicode routines (try #2)
cifs: wrap received signature check in srv_mutex
Steve French (6):
Allow user names longer than 32 bytes
Max share size is too small
Elminate sparse __CHECK_ENDIAN__ warnings on port conversion
various endian fixes to cifs
[CIFS] cifs: clarify the meaning of tcpStatus == CifsGood
[CIFS] Warn on requesting default security (ntlm) on mount
--
Thanks,
Steve
next reply other threads:[~2011-04-12 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 1:33 Steve French [this message]
2011-04-12 11:51 ` shrinking set of cifs fixes to merge for 2.6.39 to small set Jeff Layton
[not found] ` <20110412075144.53180566-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2011-04-12 12:30 ` Steve French
[not found] ` <BANLkTin627FFHH_mt1Lu7TMVMAb5y-DKgg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-12 13:16 ` Jeff Layton
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='BANLkTi=72h+nv9BfB+1e69tW4Hb_u5U_TA@mail.gmail.com' \
--to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@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).