From: Patrick Ohly <patrick.ohly@intel.com>
To: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: oe-init-build-env slowdown: chmod -R
Date: Fri, 04 Sep 2015 08:42:54 +0200 [thread overview]
Message-ID: <1441348974.9573.42.camel@intel.com> (raw)
Hello!
The following commit introduced a "chmod -R -st" on the build dir:
commit f0d3587706fffdcc1c708013f6d6ce296dfc5f24
Author: Alex Franco <alejandro.franco@linux.intel.com>
Date: Fri Aug 28 17:34:04 2015 -0500
Fix mode +st on TMPDIR when creating it
A sanity check fails when TMPDIR has setuid, setgid set. It was
proposed to fix this on TMPDIR creation instead of failing with
a sanity test only. This patch handles removal of those special
bits (and additonally, the sticky bit) from BUILDDIR and TMPDIR
when these directories are created.
In my case (*), that chmod takes about 2 minutes to complete. strace
shows that it does a fchmodat on all files, even if nothing needs to be
changed. atop then shows that this keeps the disk 100% busy with writes.
I don't know what gets written (can't be the access time, I tried
mounting with noatime).
Are others seeing the same behavior? I can't rule out that my disk is
just slow due to fragmentation.
The following commands work much better for me. I can submit a patch if
others see the same thing.
find . -perm /+st -print0 | xargs -0 --no-run-if-empty chmod -st
(*) Debian 8, Linux 3.16.0-4-amd64, coreutils 8.23-4, ext4 on a SATA
hard disk.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next reply other threads:[~2015-09-04 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 6:42 Patrick Ohly [this message]
2015-09-04 7:18 ` oe-init-build-env slowdown: chmod -R Jussi Kukkonen
2015-09-04 7:20 ` Burton, Ross
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=1441348974.9573.42.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox