All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Wuchongyun <wu.chongyun@h3c.com>,
	Benjamin Marzinski <bmarzins@redhat.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>
Cc: Guozhonghua <guozhonghua@h3c.com>,
	Changwei Ge <ge.changwei@h3c.com>,
	Changlimin <changlimin@h3c.com>
Subject: Re: [PATCH V4] multipathd: release uxsocket and resource when cancel thread
Date: Wed, 17 Jan 2018 11:30:03 +0100	[thread overview]
Message-ID: <1516185003.9784.0.camel@suse.com> (raw)
In-Reply-To: <CEB9978CF3252343BE3C67AC9F0086A3429580E5@H3CMLB14-EX.srv.huawei-3com.com>

On Wed, 2018-01-17 at 08:15 +0000, Wuchongyun wrote:
> Hi Matin,
> I think it's a good idea to move the close(ux_sock) call further up
> to avoid new clients trying to connect, Below is the new patch for
> your comment. Please help to review. Thanks. 

IMO the patch is fine now. Let's see if Ben or someone else has further
remarks.

Reviewed-by: Martin Wilck <mwilck@suse.com>

-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2018-01-17 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17  8:15 [PATCH V4] multipathd: release uxsocket and resource when cancel thread Wuchongyun
2018-01-17 10:30 ` Martin Wilck [this message]
2018-01-17 19:05 ` Benjamin Marzinski
  -- strict thread matches above, loose matches on Subject: below --
2018-01-17  2:33 Wuchongyun
2018-01-17  7:39 ` Martin Wilck

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=1516185003.9784.0.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=bmarzins@redhat.com \
    --cc=changlimin@h3c.com \
    --cc=dm-devel@redhat.com \
    --cc=ge.changwei@h3c.com \
    --cc=guozhonghua@h3c.com \
    --cc=wu.chongyun@h3c.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.