search for: backrefs

...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 wa...

...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 resolu...

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 performance...

A user reported that fsck was complaining about unresolved refs for some snapshots. You can reproduce this by doing mkfs.btrfs /dev/sdb mount /dev/sdb /mnt btrfs subvol snap /mnt/ /mnt/a btrfs subvol snap /mnt/ /mnt/b btrfs subvol del /mnt/a umount /mnt btrfsck /dev/sdb and you''d get this unresolved ref root 258 dir 256 index 2 namelen 1 name a error 600 because snapshot b has a dir

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

...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 wh...

...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/843...

...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 vi...

[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

...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) and Extended Regular Expressions (EREs), without supporting backrefs for EREs, following POSIX strictly in this respect. And ERE...

Hi All, I''m trying to repair a broken fs using btrfsck and am hitting a failed assertion. I''d appreciate any suggestions for what to do next. Is there any thing I can do to help fix this bug? Any other information from my FS which would help? If the FS could be salvaged that would be a bonus, but I''m more interested in providing a useful bug report before wiping the

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

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,

Hi! I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot). When switching to 3.2.5 recently the system fails to boot: (after udevd) /etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc and so on, no idea. It used to boot with 3.2.4, but 1) I obviously had some corruption in the tree, when I tried to delete a certain file I hit e.g. "kernel BUG at

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

Version 0.3-7 of the gsubfn package is available on CRAN. Changes to the package are: - all known bugs have been fixed. - in gsubfn and strapply the replacement object can be a list (or a function, formula, character string or proto object, as before). In the case of a list, regexp matches are looked up in the list names and the corresponding list component used. # Example 1 - at

Version 0.3-7 of the gsubfn package is available on CRAN. Changes to the package are: - all known bugs have been fixed. - in gsubfn and strapply the replacement object can be a list (or a function, formula, character string or proto object, as before). In the case of a list, regexp matches are looked up in the list names and the corresponding list component used. # Example 1 - at