DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>
Cc: "Tyler Retzlaff" <roretzla@linux.microsoft.com>,
	"Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Maxime Coquelin" <maxime.coquelin@redhat.com>,
	"Chenbo Xia" <chenbox@nvidia.com>,
	"Tomasz Duszynski" <tduszynski@marvell.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>, <dev@dpdk.org>
Subject: RE: [PATCH v3 2/3] eal: handle sysconf(_SC_PAGESIZE) negative return value
Date: Fri, 27 Jun 2025 19:49:42 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9FD53@smartserver.smartshare.dk> (raw)
In-Reply-To: <6180155.ReJHH8Nr61@thomas>

> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Friday, 27 June 2025 19.35
> 
> 27/06/2025 18:38, Morten Brørup:
> > > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > Sent: Friday, 27 June 2025 17.58
> > >
> > > 24/06/2025 10:03, Morten Brørup:
> > > > +		if ((ssize_t)page_size < 0)
> > > > +			rte_panic("sysconf(_SC_PAGESIZE) failed: %s",
> > > > +					errno == 0 ? "Indeterminate" :
> > > strerror(errno));
> > >
> > > We don't want more rte_panic().
> > > You could log the problem and return 0 here.
> > > It will be a problem later, but it may allow the application to
> cleanup
> > > instead of abrupting crashing.
> >
> > Disagree.
> > That would be likely to cause crash with division by zero later.
> > Better to fail early.
> 
> Which division by zero?

Functions dividing by page size. E.g.:
https://elixir.bootlin.com/dpdk/v25.03/source/lib/eal/common/eal_common_memory.c#L313

> 
> I don't think a library should take this decision on behalf of the app.

I expect lots of things to break if sysconf(_SC_PAGESIZE) fails, so the purpose of this patch is to centralize error handling here, and only continue/return with non-failing values.

Otherwise, everywhere using rte_mem_page_size() or sysconf(_SC_PAGESIZE) should implement error handling (or ignore errors).
That's a lot of places, so I'm not going to provide a patch doing that.


  reply	other threads:[~2025-06-27 17:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 13:13 [PATCH] eal: handle sysconf() " Morten Brørup
2025-06-12 14:06 ` [PATCH v2] eal: handle sysconf(_SC_PAGESIZE) " Morten Brørup
2025-06-13  9:55   ` Burakov, Anatoly
2025-06-24  8:03 ` [PATCH v3 0/3] " Morten Brørup
2025-06-24  8:03   ` [PATCH v3 1/3] eal/unix: fix log message for madvise() failure Morten Brørup
2025-06-27 15:56     ` Thomas Monjalon
2025-06-27 16:47       ` Morten Brørup
2025-06-27 17:34         ` Thomas Monjalon
2025-06-27 17:51           ` Morten Brørup
2025-06-24  8:03   ` [PATCH v3 2/3] eal: handle sysconf(_SC_PAGESIZE) negative return value Morten Brørup
2025-06-27 15:58     ` Thomas Monjalon
2025-06-27 16:38       ` Morten Brørup
2025-06-27 17:35         ` Thomas Monjalon
2025-06-27 17:49           ` Morten Brørup [this message]
2025-06-27 18:30             ` Thomas Monjalon
2025-06-24  8:03   ` [PATCH v3 3/3] pmu: " Morten Brørup

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=98CBD80474FA8B44BF855DF32C47DC35E9FD53@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stephen@networkplumber.org \
    --cc=tduszynski@marvell.com \
    --cc=thomas@monjalon.net \
    /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).