All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Markus Mayer <markus.mayer@broadcom.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/popt: bump to version 1.19
Date: Fri, 18 Nov 2022 13:56:53 -0800	[thread overview]
Message-ID: <2226aa4a-b744-30ab-699c-c4316c314d4f@gmail.com> (raw)
In-Reply-To: <CAPi7W80x3ntmmr6xcKasos45siu5WpQzR9oiQB1VKsAf86OweA@mail.gmail.com>

On 11/15/22 23:25, Fabrice Fontaine wrote:
> Hi,
> 
> Le mer. 16 nov. 2022 à 00:48, Florian Fainelli <f.fainelli@gmail.com 
> <mailto:f.fainelli@gmail.com>> a écrit :
> 
>     Hi Fabrice,
> 
>     On 9/17/22 14:17, Fabrice Fontaine wrote:
>      > - Drop patches (already in version) and so autoreconf
>      > - Update hash of COPYING (license adjusted to use the original,
>     straight
>      >    MIT variant:
>      >
>     https://github.com/rpm-software-management/popt/commit/dcec86df3cfc96d3dd3a3e9f7f1086b768d2d88f <https://github.com/rpm-software-management/popt/commit/dcec86df3cfc96d3dd3a3e9f7f1086b768d2d88f>)
>      >
>      >
>     https://github.com/rpm-software-management/popt/compare/popt-1.18-release...popt-1.19-release <https://github.com/rpm-software-management/popt/compare/popt-1.18-release...popt-1.19-release>
>      >
>      > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com
>     <mailto:fontaine.fabrice@gmail.com>>
> 
>     We recently upgraded from buildroot 2022.08 to 2022.11-rc1 which
>     contains this change of yours and this causes gptfdisk's sgdisk to not
>     be able to open the devices passed as argument, steps to reproduce
>     would
>     be as simple as:
> 
>     # sgdisk -p /dev/sda
>     Problem opening  for reading! Error is 2.
>     The specified file does not exist!
> 
>     Markus looked at the strace output and found the following:
> 
>     strace -f sgdisk -p /dev/sda
>     [...]
>     brk(NULL)                               = 0x5581f4d000
>     brk(0x5581f6e000)                       = 0x5581f6e000
>     brk(0x5581f8f000)                       = 0x5581f8f000
>     openat(AT_FDCWD, "", O_RDONLY)          = -1 ENOENT (No such file or
>     directory)
>     write(2, "Problem opening ", 16Problem opening )        = 16
>     write(2, " for reading! Error is ", 23 for reading! Error is ) = 23
>     write(2, "2", 12)                        = 1
>     write(2, ".\n", 2.
>     )                      = 2
>     write(2, "The specified file does not exis"..., 35The specified file
>     does not exist!
>     ) = 35
>     exit_group(2)                           = ?
>     +++ exited with 2 +++
> 
>     the openat() system call is passed an empty string which is the reason
>     for sgdisk to fail opening the specified device. Reverting libpopt back
>     to 1.18 but keeping everything else the same resolves the issue.
> 
>     Is this is a known problem? Thanks!
> 
> 
> Yes, this is a known issue raised because the value returned by 
> poptGetArg() doesn't leak anymore:
> https://github.com/rpm-software-management/popt/issues/80 
> <https://github.com/rpm-software-management/popt/issues/80>
> 
> I'll send a patch to apply the gptfdisk partial fix mentioned above.

Thanks much appreciated!
-- 
Florian

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-11-18 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 21:17 [Buildroot] [PATCH 1/1] package/popt: bump to version 1.19 Fabrice Fontaine
2022-09-21 20:09 ` Thomas Petazzoni
2022-11-15 23:48 ` Florian Fainelli
2022-11-16  7:25   ` Fabrice Fontaine
2022-11-18 21:56     ` Florian Fainelli [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=2226aa4a-b744-30ab-699c-c4316c314d4f@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=markus.mayer@broadcom.com \
    --cc=thomas.petazzoni@bootlin.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.