Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] busybox: add patch to fix seg fault in 'ifup -a'
Date: Fri, 16 Nov 2018 20:29:01 +0100	[thread overview]
Message-ID: <87d0r4stxe.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+1k=2b2EPjS_JBF__mVhgaLcJc22P=nCp-BSzo2hdLPwzp0Eg@mail.gmail.com> (Joel Carlson's message of "Fri, 16 Nov 2018 09:35:09 -0700")

>>>>> "Joel" == Joel Carlson <JoelsonCarl@gmail.com> writes:

Hi,

 >> Busybox 1.29.3, which is on Buildroot master since commit 77497f5497,
 >> aleady has this fix:
 >> 
 >> Applying 0004-libbb-in-xmalloc_fgets-use-size_t-for-bb_get_chunk_f.patch using patch:
 >> patching file libbb/get_line_from_file.c
 >> Reversed (or previously applied) patch detected!  Skipping patch.
 >> 
 >> What Busybox version are you using? Perhaps your patch could be
 >> applied on the LTS branches but I think we should just bump it
 >> to 1.29.3 on those branches too.
 >> 
 >> Peter?

 > I'm not Peter (obviously), but I'd recommend bumping the buildroot
 > version on any LTS branches still using busybox 1.29.2.  I have a
 > branch off of 2018.08, and I was hitting the same segfault issue until
 > I cherry-picked the commit from master that bumps busybox to 1.29.3.
 > The only change between 1.29.2 and 1.29.3 was the commit to fix this
 > issue.

2018.02.x (our LTS branch) is using 1.27.2 that afaik is not affected by
this ifup issue.

2018.08.x still had 1.29.2, so I've bumped that to 1.29.3.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-11-16 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181110193319.1273-1-daniel.m@sent.com>
2018-11-10 22:30 ` [Buildroot] [PATCH 1/1] busybox: add patch to fix seg fault in 'ifup -a' Carlos Santos
2018-11-16 16:35   ` Joel Carlson
2018-11-16 19:29     ` Peter Korsgaard [this message]
2018-11-19  0:05       ` Daniel Mentz
2018-11-19  7:48         ` Peter Korsgaard

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=87d0r4stxe.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.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