search for: backpointer

...found 40 block 152387469312 rec extent_item_refs 1, passed 1 warning, start mismatch 449606139904 427217858560 block 427217858560 rec extent_item_refs 1, passed 1 ref mismatch on [32215040 4096] extent item 30, found 31 Backref 32215040 parent 427255582720 root 427255582720 not found in extent tree backpointer mismatch on [32215040 4096] ... [snipped several thousand lines similar to the previous three] ... ref mismatch on [477808889856 4096] extent item 11, found 12 Backref 477808889856 parent 427202011136 root 427202011136 not found in extent tree backpointer mismatch on [477808889856 4096] Errors fo...

...3.920013] RIP [<ffffffffa0197cd0>] cow_file_range+0x3d0/0x4b0 [btrfs] [ 153.920013] RSP <ffff8801a1fb1580> [ 153.920330] ---[ end trace 462486d382b33cae ]--- Btrfsck on this volume prints a lot of messages about incorrect backrefs, and eventually fails out due to bad key ordering: backpointer mismatch on [823847440384 1204224] owner ref check failed [823847440384 1204224] ref mismatch on [823848644608 1269760] extent item 1, found 0 Incorrect local backref count on 823848644608 root 5 owner 136598 offset 0 found 0 wanted 1 back 0xa6 cc9a0 backpointer mismatch on [823848644608 1269760] o...

...btrfsck which previously used to fail: # btrfsck /dev/sda1 Extent back ref already exists for 9872289792 parent 0 root 5 leaf parent key incorrect 9872289792 bad block 9872289792 ref mismatch on [9872289792 4096] extent item 1, found 2 Incorrect global backref count on 9872289792 found 1 wanted 2 backpointer mismatch on [9872289792 4096] owner ref check failed [9872289792 4096] ref mismatch on [9889067008 4096] extent item 1, found 0 Backref 9889067008 root 5 not referenced Incorrect global backref count on 9889067008 found 1 wanted 0 backpointer mismatch on [9889067008 4096] owner ref check failed [98...

Dear All: I am pretty new to xen-devel, please correct me in the following. Assume we have the following terms GPT: guest page table SPT: shadow page table (Question a) When guest OS is running, is it always using SPT for address translation? If it is the case, how does guest OS refer and modify its own GPT content? It seems that there is a page table entry in SPT for the GPT page. (Question

....profile() > gc() As long as I don't execute memory.profile(), there is no problem with garbage collection. So I think that memory.profile() screws up the heap in some way. When it seg-faults, it dies in the function compactPhase() in memory.c, while (vfrom < R_VTop) { s = BACKPOINTER(*vfrom); switch (TYPEOF(s)) { /* get size in bytes */ /* <- dies here */ it segfaults becuase s becomes a pointer to 0x0, when the while loop is almost finishing, i.e., vfrom is close to R_VTop (vfrom = 0x20001840ef8 and R_VTop = 0x20001841198). I tried to see what's going on i...

Signed-off-by: Anand Jain <anand.jain@oracle.com> --- mkfs.c | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/mkfs.c b/mkfs.c index de1beed..0843600 100644 --- a/mkfs.c +++ b/mkfs.c @@ -1196,8 +1196,7 @@ static void process_fs_features(u64 flags) for (i = 0; i < ARRAY_SIZE(mkfs_features); i++) { if (flags & mkfs_features[i].flag) { - fprintf(stderr,

Is it expected that running btrfsck more than once will keep reporting errors? Below is the end of a btrfsck output when run the second time. backpointer mismatch on [111942471680 32768] owner ref check failed [111942471680 32768] ref mismatch on [111942504448 40960] extent item 1, found 0 Incorrect local backref count on 111942504448 root 5 owner 160739 offset 3440640 found 0 wanted 1 back 0x14331f48 backpointer mismatch on [111942504448 40960] ow...

On Wed, Apr 14, 2010 at 5:45 PM, Neal N. Wang <neal.wang at gmail.com> wrote: > Thanks for all the replies which are really helpful. > > one more question regarding transformation: > > 4.  Given an instruction  %x1 = I1,  can I replace the rhs "I1"  with  "I2" > and get a new instruction %x1 = I2?   Alternatively, I can add a new > instruction %x2 =

On 2017?01?27? 16:16, Christoph Hellwig wrote: > We don't really need struct virtio_pci_vq_info, as most field in there > are redundant: > > - the vq backpointer is not strictly neede to start with > - the entry in the vqs list is not needed - the generic virtqueue already > has list, we only need to check if it has a callback to get the same > semantics > - we can use a simple array to look up the MSI-X vec if needed. > - That...

On 2017?01?27? 16:16, Christoph Hellwig wrote: > We don't really need struct virtio_pci_vq_info, as most field in there > are redundant: > > - the vq backpointer is not strictly neede to start with > - the entry in the vqs list is not needed - the generic virtqueue already > has list, we only need to check if it has a callback to get the same > semantics > - we can use a simple array to look up the MSI-X vec if needed. > - That...

On 2017?02?06? 01:15, Christoph Hellwig wrote: > We don't really need struct virtio_pci_vq_info, as most field in there > are redundant: > > - the vq backpointer is not strictly neede to start with > - the entry in the vqs list is not needed - the generic virtqueue already > has list, we only need to check if it has a callback to get the same > semantics > - we can use a simple array to look up the MSI-X vec if needed. > - That...

On 2017?02?06? 01:15, Christoph Hellwig wrote: > We don't really need struct virtio_pci_vq_info, as most field in there > are redundant: > > - the vq backpointer is not strictly neede to start with > - the entry in the vqs list is not needed - the generic virtqueue already > has list, we only need to check if it has a callback to get the same > semantics > - we can use a simple array to look up the MSI-X vec if needed. > - That...

...t; + /** > + * @vborder: Vertical border. This values encodes both the top and > + * bottom borders: top_border = bottom_border = vborder / 2. > + */ > + unsigned int vborder; > +}; > + > /** > * struct drm_connector_state - mutable connector state > * @connector: backpointer to the connector > @@ -429,6 +475,12 @@ struct drm_connector_state { > * protection. This is most commonly used for HDCP. > */ > unsigned int content_protection; > + > + /** > + * @underscan: Underscan information. Most commonly used to adjust > + * image when the...

Thanks for all the replies which are really helpful. one more question regarding transformation: 4. Given an instruction %x1 = I1, can I replace the rhs "I1" with "I2" and get a new instruction %x1 = I2? Alternatively, I can add a new instruction %x2 = I2, and replace all uses of %x1 with %x2, and then delete %x1 = I1, but it seems the former is simpler or faster if

...= hborder / 2. + */ + unsigned int hborder; + + /** + * @vborder: Vertical border. This values encodes both the top and + * bottom borders: top_border = bottom_border = vborder / 2. + */ + unsigned int vborder; +}; + /** * struct drm_connector_state - mutable connector state * @connector: backpointer to the connector @@ -429,6 +475,12 @@ struct drm_connector_state { * protection. This is most commonly used for HDCP. */ unsigned int content_protection; + + /** + * @underscan: Underscan information. Most commonly used to adjust + * image when the display is doing overscan. + */ + struc...

Hello, This is an attempt at providing generic support for underscan connector props. We already have 3 drivers defining the same underscan, underscan vborder and underscan hborder properties (amd, radeon and nouveau) and I am about to add a new one, hence my proposal to put the prop parsing code in the core and add ->underscan fields to drm_connector_state. Note that I use this new

...rder. This values encodes both the top and > > + * bottom borders: top_border = bottom_border = vborder / 2. > > + */ > > + unsigned int vborder; > > +}; > > + > > /** > > * struct drm_connector_state - mutable connector state > > * @connector: backpointer to the connector > > @@ -429,6 +475,12 @@ struct drm_connector_state { > > * protection. This is most commonly used for HDCP. > > */ > > unsigned int content_protection; > > + > > + /** > > + * @underscan: Underscan information. Most commonly used...

We don't really need struct virtio_pci_vq_info, as most field in there are redundant: - the vq backpointer is not strictly neede to start with - the entry in the vqs list is not needed - the generic virtqueue already has list, we only need to check if it has a callback to get the same semantics - we can use a simple array to look up the MSI-X vec if needed. - That simple array now also duoble s...

We don't really need struct virtio_pci_vq_info, as most field in there are redundant: - the vq backpointer is not strictly neede to start with - the entry in the vqs list is not needed - the generic virtqueue already has list, we only need to check if it has a callback to get the same semantics - we can use a simple array to look up the MSI-X vec if needed. - That simple array now also duoble s...

...7fd272aea32388570503f00d0ab592fc2a Mon Sep 17 00:00:00 2001 From: Christoph Hellwig <hch at lst.de> Date: Wed, 25 Jan 2017 13:40:21 +0100 Subject: virtio_pci: remove struct virtio_pci_vq_info We don't really need struct virtio_pci_vq_info, as most field in there are redundant: - the vq backpointer is not strictly neede to start with - the entry in the vqs list is not needed - the generic virtqueue already has list, we only need to check if it has a callback to get the same semantics - we can use a simple array to look up the MSI-X vec if needed. - That simple array now also duoble s...