All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	Mirza Krak <mirza.krak@gmail.com>
Cc: Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: ROOTFS_RPM_DEBUG undocumented
Date: Tue, 8 May 2018 13:29:48 +0300	[thread overview]
Message-ID: <f58fc6cd-43fb-4fc6-c196-1aeb9ea7288d@linux.intel.com> (raw)
In-Reply-To: <166e9515231b4c9da6395957d58a75bb@XBOX02.axis.com>

On 05/08/2018 12:33 PM, Peter Kjellerstedt wrote:
> FYI, the already applied patch only solves half the problem. I have an
> updated version that solves all of it that I am preparing for publication.
> I only need to make some verifications first...

I just found that out as well. Lua is not relevant, we don't even enable 
or build it. Anyway, I've been fighting*scratch*convincing upstream all 
morning that fcntl bombs are a real problem under Docker, you are 
welcome to join :)

https://bugzilla.redhat.com/show_bug.cgi?id=1537564

Alex


      reply	other threads:[~2018-05-08 10:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 10:42 ROOTFS_RPM_DEBUG undocumented Paulo Neves
2018-05-03 13:03 ` Alexander Kanavin
2018-05-03 13:37   ` Peter Kjellerstedt
2018-05-03 14:21     ` Alexander Kanavin
2018-05-04 12:42   ` Paulo Neves
2018-05-04 12:41     ` Alexander Kanavin
2018-05-04 12:43       ` Alexander Kanavin
2018-05-04 12:50       ` Scott Rifenbark
2018-05-04 12:45         ` Alexander Kanavin
2018-05-04 12:55       ` Paulo Neves
2018-05-07  9:03       ` Mirza Krak
2018-05-07 10:12         ` Alexander Kanavin
2018-05-08  9:33           ` Peter Kjellerstedt
2018-05-08 10:29             ` Alexander Kanavin [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=f58fc6cd-43fb-4fc6-c196-1aeb9ea7288d@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=mirza.krak@gmail.com \
    --cc=peter.kjellerstedt@axis.com \
    --cc=yocto@yoctoproject.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.