public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH v2] dpkg: acquire a read (shared) locks while building packages
Date: Fri, 15 Mar 2019 05:47:28 +0100	[thread overview]
Message-ID: <fbec7283-440c-d1b9-1371-6c9b87787f80@ilbers.de> (raw)
In-Reply-To: <1552060145-1317-1-git-send-email-Cedric_Hombourger@mentor.com>

On 3/8/19 4:49 PM, Cedric Hombourger wrote:
> As debhelper scripts involved during the actual build process
> (dpkg-buildpackage) may access the dpkg database, we need to
> make sure it does not get modified in the background by other
> build tasks for other packages (such as install_build_deps).
> An example of a reader is dh_shlibdeps/dpkg-shlibdeps: it
> needs to find packages providing the shared libraries the
> package depends on to substitute shlibs variables found in its
> control file with package dependencies. Acquire the isar-apt
> lock as a shared lock to block writers.
> 
> Special care may be needed in other classes/users of the
> dpkg_runbuild API. Due to some limitations with bitbake (to be
> discussed with the maintainers), we could not grab the lock
> from dpkg-base. A statement such as "flock <my-lock.lock>
> dpkg_run_build" would fail as flock can't exec() dpkg_run_build
> (since it is a shell function, not an executable). The popular
> shell construct "( flock -n 9; dpkg_run_build ) 9> <my-lock.lock>"
> cannot be parsed by bitbake. And finally the lockfiles task
> attribute (implemented in bitbake) only handles exclusive locks.
> 
> This commit is only addressing dpkg.bbclass. dpkg-raw.bbclass
> is left intact as the generated control file does require
> dh_shlibdeps. linux-custom.inc was also left out as the Debian
> packaging scripts only use low-level packaging tools and do not
> use debhelper scripts during packaging (at this time). In
> agreement with the Isar project maintainers, we will not grab
> the Isar lock from linux-custom.inc to let kernel builds run
> in parallel with do_install_deps() and do_deploy_deb() that
> may be executed by other bitbake threads.

Applied to the 'next'.

Thanks,
Maxim.

> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
> ---
>   meta/classes/dpkg.bbclass | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
> index 24b9fe3..f4e3d7a 100644
> --- a/meta/classes/dpkg.bbclass
> +++ b/meta/classes/dpkg.bbclass
> @@ -19,5 +19,6 @@ do_install_builddeps[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
>   # Build package from sources using build script
>   dpkg_runbuild() {
>       E="${@ bb.utils.export_proxies(d)}"
> +    flock -s "${REPO_ISAR_DIR}/isar.lock" \
>       sudo -E chroot --userspec=$( id -u ):$( id -g ) ${BUILDCHROOT_DIR} /isar/build.sh ${PP}/${PPS} ${DISTRO_ARCH}
>   }
> 


-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

      parent reply	other threads:[~2019-03-15  4:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08  9:57 [PATCH] " Cedric Hombourger
2019-03-08 10:04 ` Jan Kiszka
2019-03-08 13:33   ` cedric_hombourger
2019-03-08 15:13     ` Jan Kiszka
2019-03-08 15:24       ` cedric_hombourger
2019-03-08 15:27         ` Jan Kiszka
2019-03-08 15:49           ` [PATCH v2] " Cedric Hombourger
2019-03-08 16:38             ` Jan Kiszka
2019-03-14  6:21               ` cedric_hombourger
2019-03-15  4:47             ` Maxim Yu. Osipov [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=fbec7283-440c-d1b9-1371-6c9b87787f80@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=Cedric_Hombourger@mentor.com \
    --cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox