All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Pgowda <pgowda.cve@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org,
	Randy MacLeod <rwmacleod@gmail.com>,
	umesh.kalappa0@gmail.com, Vinay Kumar <vinay.m.engg@gmail.com>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: [OE-core] [PATCH] state/staging: Fix directory not deleted for race
Date: Tue, 28 Sep 2021 11:12:25 -0400	[thread overview]
Message-ID: <9a55811d-b950-281f-1f7a-f12b39a2ef9b@windriver.com> (raw)
In-Reply-To: <CALY4984U1txY2y6yJQQKts20Hb6x-86gtXhHx9UoEeDxF1yyTg@mail.gmail.com>

Add Khem (aka Mr Musl). ;-)

On 2021-09-16 4:28 a.m., Pgowda wrote:
> Hi Richard,
> 
> Thanks for reviewing the patch and your comments.
> 
>> Looking further at this and your description, I think you might be saying there
>> are multiple levels of empty directories.
> 
> Yes. There are multiple level of directories as follows:-
> 
> /tmp/work/x86_64-linux/rust-cross-x86_64/1.54.0-r0/recipe-sysroot\
> /usr/include/c++/11.2.0/x86_64-poky-linux/ext
> /tmp/work/x86_64-linux/rust-cross-x86_64/1.54.0-r0/recipe-sysroot\
> /usr/include/c++/11.2.0/x86_64-poky-linux/bits
> /tmp/work/x86_64-linux/rust-cross-x86_64/1.54.0-r0/recipe-sysroot\
> /usr/include/c++/11.2.0/x86_64-poky-linux
> 
>> I would also like to understand why these files overlap and are symlinks in one
>> case but directories in another. Can you show some specific examples of the
>> files in question?
> 
> It happens when we build rust-hello-world for glibc followed by musl
> as follows:-
> TCLIBC=glibc MACHINE=qemuarm bitbake rust-hello-world
> TCLIBC=musl MACHINE=qemuarm bitbake rust-hello-world
> 
> The recipe do_prepare_recipe_sysroot tries to populate the sysroot file.
> The glibc build had already generated the sysroot and copied properly.
> When we build the musl later on, it tries to remove the above
> directory and symlink
> the newly built musl files. It was deleted properly before the race
> issue was observed.
> However, after the race issue; files are being deleted but the
> directory and sub directories
> are left undeleted which resulted in the error.


All of that makes sense to me based on first reading it but I'm not
intimately familiar with toolchain sysroot setup.

> 
>> The missing json file sounds like there could be some file not being handled by
>> sstate but it is hard to know without looking at the code.
> 
> Thanks. I will try to debug the issue further.


So do you have additional information Naveen or
do you maintain that the fix presented on this thread is all that is needed.

../Randy

> 
> Regards,
> pgowda
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#156105): https://lists.openembedded.org/g/openembedded-core/message/156105
> Mute This Topic: https://lists.openembedded.org/mt/85625195/3616765
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
# Randy MacLeod
# Wind River Linux



  reply	other threads:[~2021-09-28 15:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 11:46 [PATCH] state/staging: Fix directory not deleted for race Pgowda
2021-09-16  7:45 ` Richard Purdie
     [not found] ` <16A53DBD300C0C8E.4388@lists.openembedded.org>
2021-09-16  7:53   ` [OE-core] " Richard Purdie
2021-09-16  8:28     ` Pgowda
2021-09-28 15:12       ` Randy MacLeod [this message]
2021-09-28 20:21       ` Richard Purdie
2021-10-01  7:24         ` [PATCH v2] " Pgowda
2021-10-18 12:53           ` Richard Purdie
2021-10-18 13:47             ` pgowda cve
2021-10-18 14:52               ` Richard Purdie
2021-10-18 14:59                 ` [OE-core] " Martin Jansa
2021-10-19  4:43                 ` pgowda cve
2021-10-01  7:28         ` [OE-core] [PATCH] " pgowda cve
     [not found]         ` <16A9D78EAA10C9CD.7289@lists.openembedded.org>
2021-10-18  7:43           ` pgowda cve

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=9a55811d-b950-281f-1f7a-f12b39a2ef9b@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pgowda.cve@gmail.com \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=rwmacleod@gmail.com \
    --cc=umesh.kalappa0@gmail.com \
    --cc=vinay.m.engg@gmail.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.