From: Tiwei Bie <tiwei.bie@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, jianfeng.tan@intel.com, yliu@fridaylinux.org,
zhihong.wang@intel.com, xiao.w.wang@intel.com,
cunming.liang@intel.com, dan.daly@intel.com
Subject: Re: [PATCH 1/3] vhost: do not generate signal when sendmsg fails
Date: Thu, 29 Mar 2018 21:46:49 +0800 [thread overview]
Message-ID: <20180329134649.cykuce2k3biieo7j@debian> (raw)
In-Reply-To: <1dadbc4a-8ca8-c1b8-ff36-417fc1395a23@redhat.com>
On Thu, Mar 29, 2018 at 03:41:23PM +0200, Maxime Coquelin wrote:
> On 03/29/2018 03:25 PM, Tiwei Bie wrote:
> > On Thu, Mar 29, 2018 at 02:19:35PM +0200, Maxime Coquelin wrote:
> > > Hi Tiwei,
> > >
> > > On 03/06/2018 11:43 AM, Tiwei Bie wrote:
> > > > Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> > >
> > > Could you please elaborate a bit more why this is needed?
> > > Is it fixing a real issue or just an improvement?
> >
> > My bad, I really should write a more useful commit log..
> >
> > I saw your comments on this mail:
> >
> > http://dpdk.org/ml/archives/dev/2018-March/094201.html
> >
> > Thank you so much! :-)
> >
> > It's fixing an issue I met when adding the vDPA support.
> > SIGPIPE would be generated when sending messages via a
> > closed slave fd, and it will terminate the process by
> > default. But as a library, we shouldn't crash the process
> > in this case, instead we just need to return with an error.
> > I didn't meet this issue without my vDPA related changes,
> > so I didn't put a fixline on it. That is to say, I'm
> > treating it as an improvement.
>
> Great, thanks for the details!
> I'll apply the patch with below commit message.
Thank you very much! :-)
Best regards,
Tiwei Bie
>
> Maxime
> >
> > Below is the commit log for your reference:
> >
> > ------ START HERE ------
> >
> > vhost: do not generate signal when sendmsg fails
> >
> > More precisely, do not generate a SIGPIPE signal if the peer
> > has closed the connection. Otherwise, it will terminate the
> > process by default. As a library, we should avoid terminating
> > the application process when error happens and just need to
> > return with an error.
> >
> > ------ END HERE ------
> >
> > Thanks again! :-)
> >
> > Best regards,
> > Tiwei Bie
> >
> > >
> > > Thanks!
> > > Maxime
> > > > ---
> > > > lib/librte_vhost/socket.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/lib/librte_vhost/socket.c b/lib/librte_vhost/socket.c
> > > > index 0354740fa..d703d2114 100644
> > > > --- a/lib/librte_vhost/socket.c
> > > > +++ b/lib/librte_vhost/socket.c
> > > > @@ -181,7 +181,7 @@ send_fd_message(int sockfd, char *buf, int buflen, int *fds, int fd_num)
> > > > }
> > > > do {
> > > > - ret = sendmsg(sockfd, &msgh, 0);
> > > > + ret = sendmsg(sockfd, &msgh, MSG_NOSIGNAL);
> > > > } while (ret < 0 && errno == EINTR);
> > > > if (ret < 0) {
> > > >
next prev parent reply other threads:[~2018-03-29 13:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 10:43 [PATCH 0/3] Extend vhost to support VFIO based accelerator Tiwei Bie
2018-03-06 10:43 ` [PATCH 1/3] vhost: do not generate signal when sendmsg fails Tiwei Bie
2018-03-29 12:19 ` Maxime Coquelin
2018-03-29 13:25 ` Tiwei Bie
2018-03-29 13:41 ` Maxime Coquelin
2018-03-29 13:46 ` Tiwei Bie [this message]
2018-03-29 13:46 ` Maxime Coquelin
2018-03-06 10:43 ` [PATCH 2/3] vhost: support sending fds via send_vhost_message() Tiwei Bie
2018-03-29 12:23 ` Maxime Coquelin
2018-03-29 12:27 ` Maxime Coquelin
2018-03-06 10:43 ` [PATCH 3/3] vhost: support VFIO based accelerator Tiwei Bie
2018-03-06 14:24 ` Maxime Coquelin
2018-03-07 8:59 ` Tiwei Bie
2018-04-18 5:49 ` [PATCH v2] " Tiwei Bie
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=20180329134649.cykuce2k3biieo7j@debian \
--to=tiwei.bie@intel.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=xiao.w.wang@intel.com \
--cc=yliu@fridaylinux.org \
--cc=zhihong.wang@intel.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.