From: Sam Liddicott <sam@liddicott.com>
To: bitbake-devel@lists.openembedded.org
Subject: pseudo abort with req '/proc/self/fd/3'
Date: Wed, 28 Feb 2024 15:31:48 +0000 [thread overview]
Message-ID: <CAOj-5WALHrqvDkVbSe4YdjF-Ad-D=Qn4DQNYAhSg5Sw3fzKxDQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
On a kirkstone build I just got an unexpected and reproducible do_install
abort:
| abort()ing pseudo client by server request. See
https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
... path mismatch [1 link]: ino 594677 db '/.../common/config/private' req
'/proc/self/fd/3'
A conflict with /proc is most surprising, why is that even in the pseudo
database?
Adding this line to the global config fixed it consistently:
PSEUDO_IGNORE_PATHS:append=",/proc,/dev,/sys"
But I wondered how there was a conflict, and then I looked again at the
abort message.
Is it possible that pseudo only uses inode number without the dev node as
the key?
struct stat {
dev_t st_dev; /* ID of device containing file */
ino_t st_ino; /* Inode number */
I would think that only the combination of both is unique across the system.
If dev_t is not part of the key, then I suggest that all paths are ignored
that are not on the same dev_t as the workspace.
Sam
[-- Attachment #2: Type: text/html, Size: 1930 bytes --]
reply other threads:[~2024-02-28 15:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAOj-5WALHrqvDkVbSe4YdjF-Ad-D=Qn4DQNYAhSg5Sw3fzKxDQ@mail.gmail.com' \
--to=sam@liddicott.com \
--cc=bitbake-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).