From: Steve French <smfrench@gmail.com>
To: Ronnie Sahlberg <lsahlber@redhat.com>
Cc: linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH 0/1] cifs: fix race between compound_send_recv() and the
Date: Thu, 14 Nov 2019 12:40:03 -0600 [thread overview]
Message-ID: <CAH2r5mtbu4PJCW4NN6798S-KcBqwMfbhtAJ_fjZzur92KHh5nA@mail.gmail.com> (raw)
In-Reply-To: <20191114061646.22122-1-lsahlber@redhat.com>
Added cc:stable (also to Pavel's patch) and merged into cifs-2.6.git
for-next and also updated the github branch used by the buildbot
On Thu, Nov 14, 2019 at 12:17 AM Ronnie Sahlberg <lsahlber@redhat.com> wrote:
>
> Steve, Pavel,
>
> I don't get any leaks on open() any more with this patch
> and no leaks on close() with Pavels patch.
>
> version 2:
> Use is_interrupt_rc() to decide if we should flag the mid as cancelled.
>
>
--
Thanks,
Steve
prev parent reply other threads:[~2019-11-14 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 6:16 [PATCH 0/1] cifs: fix race between compound_send_recv() and the Ronnie Sahlberg
2019-11-14 6:16 ` [PATCH] cifs: fix race between compound_send_recv() and the demultiplex thread Ronnie Sahlberg
2019-11-15 18:07 ` Pavel Shilovsky
2019-11-20 23:57 ` Pavel Shilovsky
2019-11-21 0:09 ` Steve French
2019-11-21 19:34 ` Pavel Shilovsky
2019-11-14 18:40 ` Steve French [this message]
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=CAH2r5mtbu4PJCW4NN6798S-KcBqwMfbhtAJ_fjZzur92KHh5nA@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
/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).