search for: uuid_t

....c +++ b/utils/isohybrid.c @@ -36,14 +36,19 @@ #include <unistd.h> #include <sys/stat.h> #include <inttypes.h> +#include <uuid/uuid.h> #include "isohybrid.h" char *prog = NULL; extern int opterr, optind; +struct stat isostat; +unsigned int padding = 0; + +uuid_t disk_uuid, part_uuid, iso_uuid; uint8_t mode = 0; -enum { VERBOSE = 1 }; +enum { VERBOSE = 1 , EFI = 2 , MAC = 4}; /* user options */ uint16_t head = 64; /* 1 <= head <= 256 */ @@ -61,10 +66,150 @@ uint16_t ve[16]; uint32_t catoffset = 0; uint32_t c = 0, cc = 0, cs = 0;...

On Thu, May 4, 2017 at 2:21 AM, Andy Shevchenko <andriy.shevchenko at linux.intel.com> wrote: > acpi_evaluate_dsm() and friends take a pointer to a raw buffer of 16 > bytes. Instead we convert them to use uuid_le type. At the same time we > convert current users. > > acpi_str_to_uuid() becomes useless after the conversion and it's safe to > get rid of it. > > The

...eal > than mine. > > IMO, you should acknowledge that the common use case for filesystems > is > to handle an opaque char[16] which most likely holds a uuid_be and you > should provide 'neutral' helpers to satisfy this use case. > > The simplest would be to typedef uuid_t to struct uuid_be and to name > 'neutral' > helpers' uuid_cmp/uuid_copy(uuid_t *, uuid_t *), similar to my > proposal. > I think with this semantic change, our proposals can reach common > grounds > and satisfy a wider group of users (i.e. filesystem developers). >...

I have two questions about the CRAN machines that build binary packages for Mac. When a new version of a package is released, (A) Do the downstream dependencies get re-checked? (B) Do the downstream dependencies get re-built? I have heard (but do not know for sure) that the answer to (A) is no, the downstream dependencies do not get rechecked. >From publicly available information on the

...ead(mbr, 1, MBRSIZE, fp); > - if (ferror(fp)) > + if (ferror(fp) || ret != MBRSIZE) > err(1, "error while reading MBR template file `%s'", path); > fclose(fp); > } Shouldn't that be in a separate commit? > @@ -786,6 +786,21 @@ reverse_uuid(uuid_t uuid) > t = p[6]; p[6] = p[7]; p[7] = t; > } > > +static uint16_t * > +ascii_to_utf16le(uint16_t *dst, const char *src) > +{ > + uint8_t *p = (uint8_t *)dst; > + char c; > + > + do { > + c = *src++; > + *p++ = c; > + *p++ = 0; > + } while (...

...virtio_dma_buf_get_uuid - gets the uuid of the virtio dma-buf's exported object > + * @dma_buf: [in] buffer to query > + * @uuid: [out] the uuid > + * > + * Returns: 0 on success, negative on failure. > + */ > +int virtio_dma_buf_get_uuid(struct dma_buf *dma_buf, > + uuid_t *uuid) > +{ > + const struct virtio_dma_buf_ops *ops = container_of( > + dma_buf->ops, const struct virtio_dma_buf_ops, ops); > + > + if (!is_virtio_dma_buf(dma_buf)) > + return -EINVAL; > + > + return ops->get_uuid(dma_buf, uuid); > +} > +EXPORT_SYMBOL(virtio...

...virtio_dma_buf_get_uuid - gets the uuid of the virtio dma-buf's exported object > + * @dma_buf: [in] buffer to query > + * @uuid: [out] the uuid > + * > + * Returns: 0 on success, negative on failure. > + */ > +int virtio_dma_buf_get_uuid(struct dma_buf *dma_buf, > + uuid_t *uuid) > +{ > + const struct virtio_dma_buf_ops *ops = container_of( > + dma_buf->ops, const struct virtio_dma_buf_ops, ops); > + > + if (!is_virtio_dma_buf(dma_buf)) > + return -EINVAL; > + > + return ops->get_uuid(dma_buf, uuid); > +} > +EXPORT_SYMBOL(virtio...

...'r', 0, 'i', 0, 'd', 0, 0, 0}; if (mac_lba) { /* 2048 bytes per partition, plus round to 2048 boundary */ @@ -793,7 +798,7 @@ initialise_gpt(uint8_t *gpt, uint32_t current, uint32_t alternate, int primary) memcpy(part->partTypeGUID, basic_partition, sizeof(uuid_t)); part->firstLBA = lendian_64(0); part->lastLBA = lendian_64(psize); - memcpy(part->name, "ISOHybrid ISO", 28); + memcpy(part->name, part_name_iso, 28); gpt += sizeof(struct gpt_part_header); part++; @@ -802,7 +807,7 @@ initialise_gpt(uint8_t *gpt,...

...on is probably much closer to the real deal than mine. IMO, you should acknowledge that the common use case for filesystems is to handle an opaque char[16] which most likely holds a uuid_be and you should provide 'neutral' helpers to satisfy this use case. The simplest would be to typedef uuid_t to struct uuid_be and to name 'neutral' helpers' uuid_cmp/uuid_copy(uuid_t *, uuid_t *), similar to my proposal. I think with this semantic change, our proposals can reach common grounds and satisfy a wider group of users (i.e. filesystem developers). Christoph also suggested a simila...

Hi, following will be 6 patch proposals for isohybrid.c 1: Encode GPT partition names as UTF-16LE 2: Correct blocking factor in APM partition block counts 3: Correct end block address of first GPT partition 4: Write GPT backup to the very end of the image 5: Change all fseek(3) to fseeko(3) 6: Introduce option --mbr and make isohybrid.c compilable standalone If the form needs adjustments,

...x d4097856c86b..fa5210ba6aaa 100644 > --- a/drivers/dma-buf/dma-buf.c > +++ b/drivers/dma-buf/dma-buf.c > @@ -1158,6 +1158,18 @@ void dma_buf_vunmap(struct dma_buf *dmabuf, void *vaddr) > } > EXPORT_SYMBOL_GPL(dma_buf_vunmap); > > +int dma_buf_get_uuid(struct dma_buf *dmabuf, uuid_t *uuid) > +{ > + if (WARN_ON(!dmabuf) || !uuid) > + return -EINVAL; > + > + if (!dmabuf->ops->get_uuid) > + return -ENODEV; > + > + return dmabuf->ops->get_uuid(dmabuf, uuid); > +} > +EXPORT_SYMBOL_GPL(dma_buf_ge...

...x d4097856c86b..fa5210ba6aaa 100644 > --- a/drivers/dma-buf/dma-buf.c > +++ b/drivers/dma-buf/dma-buf.c > @@ -1158,6 +1158,18 @@ void dma_buf_vunmap(struct dma_buf *dmabuf, void *vaddr) > } > EXPORT_SYMBOL_GPL(dma_buf_vunmap); > > +int dma_buf_get_uuid(struct dma_buf *dmabuf, uuid_t *uuid) > +{ > + if (WARN_ON(!dmabuf) || !uuid) > + return -EINVAL; > + > + if (!dmabuf->ops->get_uuid) > + return -ENODEV; > + > + return dmabuf->ops->get_uuid(dmabuf, uuid); > +} > +EXPORT_SYMBOL_GPL(dma_buf_ge...

...+ * virtio_dma_buf_get_uuid - gets a virtio dma-buf's exported object's uuid > + * @dma_buf: [in] buffer to query > + * @uuid: [out] the uuid > + * > + * Returns: 0 on success, negative on failure. > + */ > +int virtio_dma_buf_get_uuid(struct dma_buf *dma_buf, > + uuid_t *uuid) > +{ > + const struct virtio_dma_buf_ops *ops = > + container_of(dma_buf->ops, > + const struct virtio_dma_buf_ops, ops); > + > + if (!is_virtio_dma_buf(dma_buf)) > + return -EINVAL; > + > + return ops->get_uuid(dma_buf, uuid); > +} > +EXPORT_S...

...; +#define UUID_INITIALIZED 1 > +#define UUID_INITIALIZATION_FAILED 2 > + > struct virtio_gpu_object_params { > uint32_t format; > uint32_t width; > @@ -75,6 +79,9 @@ struct virtio_gpu_object { > > bool dumb; > bool created; > + > + int uuid_state; > + uuid_t uuid; > }; > #define gem_to_virtio_gpu_obj(gobj) \ > container_of((gobj), struct virtio_gpu_object, base.base) > @@ -196,6 +203,7 @@ struct virtio_gpu_device { > bool has_virgl_3d; > bool has_edid; > bool has_indirect; > + bool has_resource_assign_uuid; > >...

...,24 @@ void __init tboot_probe(void) /* Map and check for tboot UUID. */ set_fixmap(FIX_TBOOT_SHARED_BASE, p_tboot_shared); tboot_shared = (tboot_shared_t *)fix_to_virt(FIX_TBOOT_SHARED_BASE); + if ( tboot_shared == NULL ) + return; if ( memcmp(&tboot_shared_uuid, (uuid_t *)tboot_shared, sizeof(uuid_t)) ) return; + + /* new tboot_shared (w/ GAS support) is not backwards compatible */ + if ( tboot_shared->version < 3 ) { + printk("unsupported version of tboot (%u)\n", tboot_shared->version); + return; + } g_tbo...

...+#define UUID_INITIALIZATION_FAILED 3 > + > struct virtio_gpu_object_params { > uint32_t format; > uint32_t width; > @@ -75,6 +80,9 @@ struct virtio_gpu_object { > > bool dumb; > bool created; > + > + int uuid_state; > + uuid_t uuid; > }; > #define gem_to_virtio_gpu_obj(gobj) \ > container_of((gobj), struct virtio_gpu_object, base.base) > @@ -196,6 +204,7 @@ struct virtio_gpu_device { > bool has_virgl_3d; > bool has_edid; > bool has_indirect; > + bool has_res...

...ion(+), 1 deletion(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index 7d0864e..ff6b930 100644 --- a/utils/isohybrid.c +++ b/utils/isohybrid.c @@ -797,7 +797,7 @@ initialise_gpt(uint8_t *gpt, uint32_t current, uint32_t alternate, int primary) memcpy(part->partGUID, iso_uuid, sizeof(uuid_t)); memcpy(part->partTypeGUID, basic_partition, sizeof(uuid_t)); part->firstLBA = lendian_64(0); - part->lastLBA = lendian_64(psize); + part->lastLBA = lendian_64(psize - 1); memcpy(part->name, part_name_iso, 28); gpt += sizeof(struct gpt_part_header); --...

...n] buffer to query > > > > + * @uuid: [out] the uuid > > > > + * > > > > + * Returns: 0 on success, negative on failure. > > > > + */ > > > > +int virtio_dma_buf_get_uuid(struct dma_buf *dma_buf, > > > > + uuid_t *uuid) > > > > +{ > > > > + const struct virtio_dma_buf_ops *ops = container_of( > > > > + dma_buf->ops, const struct virtio_dma_buf_ops, ops); > > > > + > > > > + if (!is_virtio_dma_buf(dma_buf)) > > > &g...

This is a Fedora Core 13 environment and I just noticed this as I update the xen-unstable tree: make -C libxl install make[3]: Entering directory `/home/konrad/ssd/xtt/xen-unstable/tools/libxl'' rm -f _libxl_paths.h.tmp.tmp; echo "SBINDIR=\"/usr/sbin\"" >> _libxl_paths.h.tmp.tmp; echo "BINDIR=\"/usr/bin\"" >> _libxl_paths.h.tmp.tmp;

I upgraded my 7.0 system to 7.1-RELEASE with freebsd-update only to find that it no longer boots correctly, instead crashing with a BTX backtrace. If I break to the loader prompt and use 'ls /boot', I also get a backtrace. A new install of 7.1 on this hardware using a separate SCSI card and drive array also leads to a BTX backtrace. I have copied this below as the first (most