search for: backref

...eeps the noise down & want to more post a notice saying "hey, here's this thing, if you're interested, go discuss it over there" - more an optional opt-in rather than requiring people to opt-out via muting the thread, etc) Yes, we can conduct the "should we enable --warn-backrefs by default" conversation here. Since the semantics --warn-backrefs of are a bit complex, we need a documentation. https://reviews.llvm.org/D86762 is put up to get wording suggestions. Explicitly adding the people to the CC list... FWIW for many code bases, --warn-backrefs should produce no w...

...wn & want to more post a notice saying "hey, here's this thing, if you're interested, go discuss it over there" - more an optional opt-in rather than requiring people to opt-out via muting the thread, etc) >> >> Yes, we can conduct the "should we enable --warn-backrefs by default" >> conversation here. Since the semantics --warn-backrefs of are a bit >> complex, we need a documentation. https://reviews.llvm.org/D86762 is >> put up to get wording suggestions. Explicitly adding the people to the >> CC list... >> >> FWIW for...

Hi all, LLD's --warn-backrefs is a tool to identify potential incompatible archive selection semantics with traditional Unix linkers. I have improved it (via D77522,D77630 and D77512) to a state where a --warn-backrefs diagnostic almost assuredly means that the link will fail with GNU ld, or the symbol will get different resol...

We''re going to use this flag EXTENT_DEFRAG to indicate which range belongs to defragment so that we can implement snapshow-aware defrag: We set the EXTENT_DEFRAG flag when dirtying the extents that need defragmented, so later on writeback thread can differentiate between normal writeback and writeback started by defragmentation. This patch is used for the latter one. Originally patch

...omium/src/+/master:build/toolchain/gcc_toolchain.gni;l=409). >In our case, compatibility with linkers on other platforms is more >important than compatibility with GNU ld, so I'd prefer to keep the current >behavior. Projects that care about compatibility with GNU ld can use >--warn-backrefs. I totally understand that some users may not want to deal with GNU ld compatibility:) I'll then question about Chromium's addition of -z defs: https://crrev.com/843583006 :) -z defs is like a layering checking tool for shared objects while --warn-backrefs is for archives. For performanc...

...t match we just give it back a empty directory since we can''t hardlink directories. This makes the check in btrfsck bogus, when we delete a we remove the ref key for it so any lookups into /mnt/b/a will just give a blank directory as it''s supposed to. Fix this by only saying the backref is reachable if there is both a DIR_ITEM and a REF_KEY for the given root. With this patch I no longer see errors when running this reproducer. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- cmds-check.c | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff...

Parents must be same after going through ref_for_same_block. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- fs/btrfs/backref.c | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c index f318793..9aaa38e6 100644 --- a/fs/btrfs/backref.c +++ b/fs/btrfs/backref.c @@ -469,11 +469,6 @@ static int __merge_refs(struct list_head *head, int mode) if (mode == 1)...

...409 >> ). >> >In our case, compatibility with linkers on other platforms is more >> >important than compatibility with GNU ld, so I'd prefer to keep the >> current >> >behavior. Projects that care about compatibility with GNU ld can use >> >--warn-backrefs. >> >> I totally understand that some users may not want to deal with GNU ld >> compatibility:) I'll then question about Chromium's addition of -z defs: >> https://crrev.com/843583006 :) >> >> -z defs is like a layering checking tool for shared objects w...

...case, compatibility with linkers on other platforms is more >> >> >important than compatibility with GNU ld, so I'd prefer to keep the >> >> current >> >> >behavior. Projects that care about compatibility with GNU ld can use >> >> >--warn-backrefs. >> >> >> >> I totally understand that some users may not want to deal with GNU ld >> >> compatibility:) I'll then question about Chromium's addition of -z defs: >> >> https://crrev.com/843583006 :) >> >> >> >> -z defs...

...tforms is more >> >> >> >important than compatibility with GNU ld, so I'd prefer to keep the >> >> >> current >> >> >> >behavior. Projects that care about compatibility with GNU ld can >> use >> >> >> >--warn-backrefs. >> >> >> >> >> >> I totally understand that some users may not want to deal with GNU >> ld >> >> >> compatibility:) I'll then question about Chromium's addition of -z >> defs: >> >> >> https://crrev.com/84...

...ite a sprawling mass, involving multiple different build systems, some bits CMake based, some hand-curated and so on, and I don't fully comprehend it all. I do know that trying to change it is hard at best, and more likely impossible to do so safely. I ran the build using an LLD with the --warn-backrefs option always enabled and saw several dozen distinct instances of the warning being emitted. I can't say how many instances of this warning are genuine library layering violations that can be easily fixed, but I can say that getting any changes to fix things (even if they are genuine and bad v...

[11558.527680] ------------[ cut here ]------------ [11558.527708] kernel BUG at fs/btrfs/transaction.c:1337! [11558.527730] invalid opcode: 0000 [#1] PREEMPT SMP [11558.527764] CPU 1 [11558.527776] Modules linked in: loop nls_cp437 vfat fat dm_mod xfs exportfs jfs usb_storage uas fuse ext4 jbd2 mbcache snd_hda_codec_hdmi snd_hda_codec_realtek arc4 iwlwifi snd_hda_intel snd_hda_codec uvcvideo

...I already have it in my branches and can provide a full implementation with tests (FileCheck now has a test/ dir all of its own since r168113) if the proposal is accepted. The rough outline of the implementation: To enable such matching in a natural way, our regex implementation needs to support backreferences in matches. This then allows to find all references to a variable defined on the same line and substitute them by backrefs. Luckily, our regex implementation already supports backreferences, although a bit of hacking is required to enable it. It supports both Basic Regular Expressions (BREs...

...wanted 26D779EB found 40 checksum verify failed on 34390753280 wanted 26D779EB 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 4272020...

I''ve upgraded to linux 3.10 and enabled extended inode refs and skinny metadata extent refs with these commands: btrfstune -r /dev/sdc1 btrfstune -x /dev/sdc1 Since then, I have "WARNING: at fs/btrfs/backref.c:903 find_parent_nodes+0x616/0x815 [btrfs]()" showing up like crazy: # grep -c "WARNING: at fs/btrfs/backref.c:903" syslog 181819 That''s after just a few hours of uptime. I guess that''s not expected? Some examples: Jul 2 21:42:59 bkp010 kernel: [ 668.547147...

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,

...things. Result: I can now actually execute 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 mismatc...

I have a string such as fileName<-"Agg.20.20.20-all-01". All I want to do is pull the "20.20.20" and the "all" as strings. Obviously, they aren't always those values. The "20.20.20" can be "30.30.30" but it's always after the . which is next to the second g in Agg and it's always the same length. The all might not always be

...In the case of a list, regexp matches are looked up in the list names and the corresponding list component used. # Example 1 - at string end replace M with e6 & G with e9 gsubfn(".$", list(M = "e6", G = "e9"), c("19G", "32.5M")) - the backref= argument in gsubfn now defaults to the negative of its prior default. Thus by default if there are back references only they and not the entire match is passed to the user function. (Although the changed default introduces an incompatibility with prior versions this incompatability is...

...In the case of a list, regexp matches are looked up in the list names and the corresponding list component used. # Example 1 - at string end replace M with e6 & G with e9 gsubfn(".$", list(M = "e6", G = "e9"), c("19G", "32.5M")) - the backref= argument in gsubfn now defaults to the negative of its prior default. Thus by default if there are back references only they and not the entire match is passed to the user function. (Although the changed default introduces an incompatibility with prior versions this incompatability is...