Nice catch. Merged a patch that applies this also.
-s
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Thu, 20 Sep 2018 20:41:02 +
wrote:
> Okay, so I found the problem, and I have a patch for it. Throughout
> the pseudo_db.c code, the handling of the msg->ino objects is not
> consistent. Many get passed to the sqlite3_bind_int64 function, but
> NOT ALL. 9 instances in the code, includin
On Wed, 19 Sep 2018 12:33:37 +0100
"Burton, Ross" wrote:
> Is anyone actually writing a patch?
I have a tentative fix for this checked into master, I don't know
whether it actually works because I don't have any inodes over 2^63.
It doesn't seem to have *broken* anything, though in casual testi
On Wed, 19 Sep 2018 12:33:37 +0100
"Burton, Ross" wrote:
> On Tue, 18 Sep 2018 at 22:21, Seebs wrote:
> > > Are the databases supposed to be shareable between different build
> > > machines? IIRC, the answer is no. Could you store the native inode
> > >
On Tue, 18 Sep 2018 16:16:22 -0500
Joshua Watt wrote:
> Are the databases supposed to be shareable between different build
> machines? IIRC, the answer is no. Could you store the native inode
> type as a sqlite BLOB? Not necessarily a good idea Just an idea.
I think coercing the values into
On Tue, 18 Sep 2018 20:26:59 +
wrote:
> SO... any suggestions how to make the inodes in the database an
> UNSIGNED value?
We probably *can't* -- sqlite doesn't support that! They cap out at 8
byte integer values, and are always signed. I don't know of a way to
fix this. We might be able to t
On Wed, 22 Aug 2018 14:54:02 +
wrote:
> So failure mode is the target filesystem is devoid of SELinux file
> contexts, all files are unlabeled_t, which pretty much breaks
> everything in enforcing mode. So whatever the corruption
> cause/effect in the Psuedo database, the end result is when
On Fri, 24 Feb 2017 16:18:38 +0100
Anton Gerasimov wrote:
> FIG_FS_POSIX_ACL=y;
> CONFIG_EXT4_FS_POSIX_ACL=y). The problem is that 'cp -a' when copying
> a directory without any ACLs attached will for whatever reason try to
> assign an empty posix_acl_default list to the target directory.
...
I
On Fri, 24 Feb 2017 15:48:15 +0100
an...@advancedtelematic.com wrote:
> From: Anton Gerasimov
>
> The difference between what we see in pseudo and what happens without
> pseudo can be seen by typing:
>
> mkdir setfattr-test
> setfattr -n system.posix_acl_default -v 0x0200 setfattr-t
