From: "Aurélien Aptel" <aaptel@suse.com>
To: Paulo Alcantara <paulo@paulo.ac>, linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, Paulo Alcantara <paulo@paulo.ac>,
Paulo Alcantara <palcantara@suse.de>,
stable@vger.kernel.org
Subject: Re: [PATCH] cifs: Fix infinite loop when using hard mount option
Date: Thu, 05 Jul 2018 19:12:51 +0200 [thread overview]
Message-ID: <871sch7gj0.fsf@suse.com> (raw)
In-Reply-To: <20180705164634.12288-1-paulo@paulo.ac>
I've debugged this with Paulo.
Reviewed-by: Aurelien Aptel <aaptel@suse.com>
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2018-07-05 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 16:46 [PATCH] cifs: Fix infinite loop when using hard mount option Paulo Alcantara
2018-07-05 17:12 ` Aurélien Aptel [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=871sch7gj0.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=palcantara@suse.de \
--cc=paulo@paulo.ac \
--cc=smfrench@gmail.com \
--cc=stable@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).