search for: offse

...ged (the system/log files are on different drives). About once a week, I get an error like this, and the partition switches to read-only. --- Feb 24 04:48:20 linbackup1 kernel: EXT3-fs error (device md3): htree_dirblock_to_tree: bad entry in directory #869973: directory entry across bloc ks - offset=0, inode=3915132787, rec_len=42464, name_len=11 Feb 24 04:48:20 linbackup1 kernel: Aborting journal on device md3. Feb 24 04:48:20 linbackup1 kernel: ext3_abort called. Feb 24 04:48:20 linbackup1 kernel: EXT3-fs error (device md3): ext3_journal_start_sb: Detected aborted journal Feb 24 04:48:20 l...

...ontained units (code, data, signature) that can be run on a high-secure falcon (currently PMU). It consumes a blob that is built by the kernel and contains the signed firmwares of the low-secure falcons to load and manage. The ACR blob is made of a header describing the managed falcons and the offses of their bootloader, code and data within the blob, as well as bootloader/code/data sections for each falcon. A signed, low-secure falcon firmware in the ACR blob is thus the aggregation of three different components: - An image containing the bl, code and data sections - A descriptor with the...

...hat can be run on a high-secure falcon (currently >> PMU). It consumes a blob that is built by the kernel and contains the signed >> firmwares of the low-secure falcons to load and manage. >> >> The ACR blob is made of a header describing the managed falcons and the >> offses of their bootloader, code and data within the blob, as well as >> bootloader/code/data sections for each falcon. >> >> A signed, low-secure falcon firmware in the ACR blob is thus the aggregation >> of three different components: >> >> - An image containing the...

...;>> PMU). It consumes a blob that is built by the kernel and contains the >>>> signed >>>> firmwares of the low-secure falcons to load and manage. >>>> >>>> The ACR blob is made of a header describing the managed falcons and the >>>> offses of their bootloader, code and data within the blob, as well as >>>> bootloader/code/data sections for each falcon. >>>> >>>> A signed, low-secure falcon firmware in the ACR blob is thus the >>>> aggregation >>>> of three different compone...

...ot v1.0.alpha5 starting up dovecot: Dec 24 16:17:51 Info: imap-login: Login: user=<will>, method=PLAIN, rip =10.0.128.58, lip=10.0.128.55 dovecot: Dec 24 16:17:51 Error: imap(will): Corrupted transaction log file /home /will/mail/.imap/test/dovecot.index.log: record size too small (type=0x20, offse t=24, size=0) dovecot: Dec 24 16:17:51 Error: imap(will): Lost transaction log file /home/will /mail/.imap/test/dovecot.index.log seq 2 dovecot: Dec 24 16:17:51 Error: imap(will): Lost transaction log file /home/will /mail/.imap/test/dovecot.index.log seq 2 dovecot: Dec 24 16:17:56 Error: imap(will...

...is built by the kernel and contains the >>>>>> signed >>>>>> firmwares of the low-secure falcons to load and manage. >>>>>> >>>>>> The ACR blob is made of a header describing the managed falcons and the >>>>>> offses of their bootloader, code and data within the blob, as well as >>>>>> bootloader/code/data sections for each falcon. >>>>>> >>>>>> A signed, low-secure falcon firmware in the ACR blob is thus the >>>>>> aggregation >>&gt...

..., data, signature) that can be run on a high-secure falcon (currently > PMU). It consumes a blob that is built by the kernel and contains the signed > firmwares of the low-secure falcons to load and manage. > > The ACR blob is made of a header describing the managed falcons and the > offses of their bootloader, code and data within the blob, as well as > bootloader/code/data sections for each falcon. > > A signed, low-secure falcon firmware in the ACR blob is thus the aggregation > of three different components: > > - An image containing the bl, code and data sectio...

...;> (currently >>> PMU). It consumes a blob that is built by the kernel and contains the >>> signed >>> firmwares of the low-secure falcons to load and manage. >>> >>> The ACR blob is made of a header describing the managed falcons and the >>> offses of their bootloader, code and data within the blob, as well as >>> bootloader/code/data sections for each falcon. >>> >>> A signed, low-secure falcon firmware in the ACR blob is thus the >>> aggregation >>> of three different components: >>> &g...

...onsumes a blob that is built by the kernel and contains the >>>>> signed >>>>> firmwares of the low-secure falcons to load and manage. >>>>> >>>>> The ACR blob is made of a header describing the managed falcons and the >>>>> offses of their bootloader, code and data within the blob, as well as >>>>> bootloader/code/data sections for each falcon. >>>>> >>>>> A signed, low-secure falcon firmware in the ACR blob is thus the >>>>> aggregation >>>>> of thr...

This patch series introduces the VHD library. It is based on the blktap2 one, with changes coming from the blktap2.5 one. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>