From: Seebs <seebs@seebs.net>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: [pseudo] Pseudo 1.8+ xattr sqlite corruption
Date: Wed, 19 Sep 2018 09:39:09 -0500 [thread overview]
Message-ID: <20180919093909.12d3fedd@seebsdell> (raw)
In-Reply-To: <CAJTo0LZ1qDr2DAFWJcHBrzWWwERYh-6eSiXNO5gcJwT=HXMb-w@mail.gmail.com>
On Wed, 19 Sep 2018 12:33:37 +0100
"Burton, Ross" <ross.burton@intel.com> wrote:
> On Tue, 18 Sep 2018 at 22:21, Seebs <seebs@seebs.net> 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 range is probably safer. It should
> > be trivial enough...
>
> That is an excellent catch and I'm hopeful that this explains the
> failures in glibc-locales too that I still see occasionally.
>
> Is anyone actually writing a patch?
I can try to get a proposed patch out sometime soon, I don't have an
easy way to check it.
-s
next prev parent reply other threads:[~2018-09-19 14:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 18:45 [pseudo] Pseudo 1.8+ xattr sqlite corruption Jack.Fewx
2018-08-22 8:41 ` Alexander Kanavin
2018-08-22 13:58 ` Jack.Fewx
2018-08-22 14:41 ` Joshua Watt
2018-08-22 14:54 ` Jack.Fewx
2018-08-22 15:09 ` Richard Purdie
2018-08-22 15:32 ` Jack.Fewx
2018-09-18 20:26 ` Jack.Fewx
2018-09-18 21:09 ` Seebs
2018-09-18 21:16 ` Joshua Watt
2018-09-18 21:20 ` Seebs
2018-09-19 11:33 ` Burton, Ross
2018-09-19 14:39 ` Seebs [this message]
2018-09-19 16:25 ` Jack.Fewx
2018-09-20 19:16 ` Seebs
2018-09-20 20:41 ` Jack.Fewx
2018-09-20 20:46 ` Seebs
2018-09-20 20:50 ` Seebs
2018-09-21 12:50 ` Burton, Ross
2018-09-23 13:23 ` Martin Jansa
2018-08-22 16:41 ` Seebs
2018-08-22 14:44 ` Alexander Kanavin
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=20180919093909.12d3fedd@seebsdell \
--to=seebs@seebs.net \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.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 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.