All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] eal: fix check when retrieving current cpu affinity
Date: Tue, 19 Feb 2019 12:55:29 +0100	[thread overview]
Message-ID: <CAJFAV8z=fG7wKXREtfyRLGqAhRv8vo1Xme9-Xa3+uL=x6+i=+g@mail.gmail.com> (raw)
In-Reply-To: <29172348-cc0c-1b36-cefc-6b3ef92137f1@intel.com>

On Tue, Feb 19, 2019 at 12:40 PM Burakov, Anatoly <anatoly.burakov@intel.com>
wrote:

> On 14-Feb-19 5:41 PM, David Marchand wrote:
> > On Thu, Feb 14, 2019 at 5:44 PM Burakov, Anatoly
> > <anatoly.burakov@intel.com <mailto:anatoly.burakov@intel.com>> wrote:
> >     CC: stable?
> >
> > Not really sure about CCing stable for this.
> >
> > I did not get errors with pthread_getaffinity_np so far.
> > Afaiu, it would need the kernel and libc to have different cpuset sizes.
> > I did not investigate in which situations it could happen.
> >
>
> You're incorrectly handling error condition - that's a bug regardless of
> how likely it is to occur :)
>

Ok will resend with Cc:


-- 
David Marchand

  reply	other threads:[~2019-02-19 11:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 13:27 [PATCH] eal: fix check when retrieving current cpu affinity David Marchand
2019-02-14 16:44 ` Burakov, Anatoly
2019-02-14 17:41   ` David Marchand
2019-02-19 11:40     ` Burakov, Anatoly
2019-02-19 11:55       ` David Marchand [this message]
2019-02-19 20:38 ` [PATCH v2] " David Marchand
2019-02-20 16:02   ` Burakov, Anatoly
2019-03-07 15:36     ` [dpdk-stable] " Thomas Monjalon
2019-02-21 18:58   ` Rami Rosen

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='CAJFAV8z=fG7wKXREtfyRLGqAhRv8vo1Xme9-Xa3+uL=x6+i=+g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.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 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.