From: Steve French <smfrench@gmail.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: list of cifs patches to be sent upstream for next rc
Date: Fri, 25 Oct 2019 18:11:03 -0500 [thread overview]
Message-ID: <CAH2r5msVwUK7Hw3H=gE0QzuQTAtxLzAECn3PK2vUDTQnu0mb-g@mail.gmail.com> (raw)
I planned to send these seven cifs/smb3 patches (current for-next)
upstream for next RC. The cifs-testing (and Windows and Azure) test
group passed with them
(http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/272)
d46b0da7a33d (HEAD -> for-next, origin/for-next) cifs: Fix
cifsInodeInfo lock_sem deadlock when reconnect occurs
1a67c4159657 CIFS: Fix use after free of file info structures
abe57073d08c CIFS: Fix retry mid list corruption on reconnects
783bf7b8b641 cifs: Fix missed free operations
03d9a9fe3f3a CIFS: avoid using MID 0xFFFF
553292a6342b cifs: clarify comment about timestamp granularity for old servers
d532cc7efdfd cifs: Handle -EINPROGRESS only when noblockcnt is set
Let me know if any objections
--
Thanks,
Steve
reply other threads:[~2019-10-25 23:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH2r5msVwUK7Hw3H=gE0QzuQTAtxLzAECn3PK2vUDTQnu0mb-g@mail.gmail.com' \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.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).