search for: unreferenced

...same configuration. See the following error messages for details: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: md1: orphan cleanup on readonly fs ext3_orphan_cleanup: deleting unreferenced inode 2010087 ext3_orphan_cleanup: deleting unreferenced inode 259361 ext3_orphan_cleanup: deleting unreferenced inode 972510 ext3_orphan_cleanup: deleting unreferenced inode 2009841 ext3_orphan_cleanup: deleting unreferenced inode 2010102 ext3_orphan_cleanup: deleting unreferenced inode 2010079 ex...

.../usr/local make_index: galeon2-1.3.4: no entry for /usr/local make_index: zh_TW-netscape-communicator-4.76: no entry for /usr/ports/www/netscape47-communicator make_index: nautilus-1.0.6_9: no entry for /usr/X11R6 make_index: nautilus-1.0.6_9: no entry for /usr/X11R6 Out of memory! Attempt to free unreferenced scalar at Tools/make_index line 44, <> chunk 8624. Attempt to free unreferenced scalar at Tools/make_index line 44, <> chunk 8624. Attempt to free unreferenced scalar at Tools/make_index line 44, <> chunk 8624. Attempt to free unreferenced scalar at Tools/make_index line 44, <&...

Hi, I'm trying to find a place where objects held in nv40_context->state.hw[] and nv40_screen->state[] are being unreferenced during pipe_context destruction. Currently I'm observing that these objects are not unreferenced and since they hold reference to buffer objects, the buffer objects themselves are not unreferenced as well (for example color buffer or z buffer). In order to clean those references I applied...

Hello, I restore a backup from all users (mail_location ...) the mail_attachment_dir backup was not from the same time. How can I the unreferenced files from mail_attachment_dir? Hardy

I'm using rsync to backup multiple directories, i.e. rsync -azq --delete --relative /dog /cat /fish user@rsync-server::modulename Everything works fine, except if I remove a directory from the list of those being backed up, it isn't deleted on the other side. For example: rsync -azq --delete --relative /dog /cat /fish user@rsync-server::modulename /dog /cat /fish are all backed up to

While doing simple IPv6 tests in KVM virtual machines, (add an IPv6 address to eth0) kmemleak complains about an unreferenced object: unreferenced object 0xffff88001e804120 (size 32): comm "softirq", pid 0, jiffies 4294900928 (age 631.544s) hex dump (first 32 bytes): 28 cb fd 1d 00 00 00 00 0c 00 00 00 01 00 01 00 (............... 02 d0 83 1d 00 00 00 00 6e 00 00 00 00 00 00 00 ........n..........

While doing simple IPv6 tests in KVM virtual machines, (add an IPv6 address to eth0) kmemleak complains about an unreferenced object: unreferenced object 0xffff88001e804120 (size 32): comm "softirq", pid 0, jiffies 4294900928 (age 631.544s) hex dump (first 32 bytes): 28 cb fd 1d 00 00 00 00 0c 00 00 00 01 00 01 00 (............... 02 d0 83 1d 00 00 00 00 6e 00 00 00 00 00 00 00 ........n..........

On Sun, Nov 07 2010 at 6:05pm -0500, Andi Kleen <andi@firstfloor.org> wrote: > On Sun, Nov 07, 2010 at 10:39:23PM +0100, Milan Broz wrote: > > On 11/07/2010 08:45 PM, Andi Kleen wrote: > > >> I read about barrier-problems and data getting to the partition when > > >> using dm-crypt and several layers so I don''t know if that could be > >

...with full LTO. I'm trying to understand where this would be an issue for full LTO, since GlobalDCE is running after inlining in the link time LTO pipeline. Just to be clear, are you concerned about the following: 1) GlobalDCE run after inlining in the "-flto -O2 -c" build removes an unreferenced available externally function 2) LTO link step would have inlined that available externally function somewhere (must be a different module since it was unreferenced in step 1) but now can't I'm not sure when 2) can happen since it had to be unreferenced in its module to be removed with my...

...rote: > > Hello, > > syzbot has tested the proposed patch but the reproducer still triggered crash: > memory leak in vhost_net_ioctl > Oh sorry for my poor patch. > ANGE): hsr_slave_1: link becomes ready > 2019/06/13 18:24:57 executed programs: 18 > BUG: memory leak > unreferenced object 0xffff88811cbc6ac0 (size 64): > comm "syz-executor.0", pid 7196, jiffies 4294943804 (age 14.770s) > hex dump (first 32 bytes): > 01 00 00 00 81 88 ff ff 00 00 00 00 82 88 ff ff ................ > d0 6a bc 1c 81 88 ff ff d0 6a bc 1c 81 88 ff ff .j.........

...rote: > > Hello, > > syzbot has tested the proposed patch but the reproducer still triggered crash: > memory leak in vhost_net_ioctl > Oh sorry for my poor patch. > ANGE): hsr_slave_1: link becomes ready > 2019/06/13 18:24:57 executed programs: 18 > BUG: memory leak > unreferenced object 0xffff88811cbc6ac0 (size 64): > comm "syz-executor.0", pid 7196, jiffies 4294943804 (age 14.770s) > hex dump (first 32 bytes): > 01 00 00 00 81 88 ff ff 00 00 00 00 82 88 ff ff ................ > d0 6a bc 1c 81 88 ff ff d0 6a bc 1c 81 88 ff ff .j.........

...age are merged with other globals of the same name when linkage occurs. This can be used to implement some forms of inline functions, templates, or other code which must be generated in each translation unit that uses it, but where the body may be overridden with a more definitive definition later. Unreferenced linkonce globals are allowed to be discarded. Note that linkonce linkage does not actually allow the optimizer to inline the body of this function into callers because it doesn’t know if this definition of the function is the definitive definition within the program or whether it will be overridden...

On Tue, Oct 24, 2017 at 9:27 PM, Vedant Kumar <vsk at apple.com> wrote: > Unreferenced linkonce globals are allowed to be discarded. > > > Is __udivmodti4 referenced? > It's referenced by a different .o file, but nothing within the module. My confusion comes from the missing direct object in the sentence. Referenced by a function local to the module? Referenced by...

...r RAID-Z pool? What is the command to perform the task? Also for COW, I understand that during the transaction (while data is been undated), ZFS keeps a copy of the previous data. However, once the transaction is successfully completed, isn''t it the case that the previous data blocks are unreferenced and can be used by future writes? So there should be no guarantee that the previous data can be recovered. Thanks This message posted from opensolaris.org

...ot the msg: Sep 23 23:29:17 blackbox kernel: EXT3-fs warning (device ide0(3,3)): ext3_clear_journal_err: detected journal error -5 from previous mount Sep 23 23:29:17 blackbox kernel: EXT3-fs: ide0(3,3): orphan cleanup on readonly fs Sep 23 23:29:17 blackbox kernel: ext3_orphan_cleanup: deleting unreferenced inode 97540 Sep 23 23:29:17 blackbox kernel: ext3_orphan_cleanup: deleting unreferenced inode 97538 Sep 23 23:29:17 blackbox kernel: EXT3-fs: ide0(3,3): 2 orphan inodes deleted the problem is that if found a part of my dpkg package list in my motd and the first line of the motd in my resolv.con...

Hello, 5.1.0-next-20190517 I'm looking at quite a lot of kmemleak reports coming from drm/nouveau/core/memory, all of which are: unreferenced object 0xffff8deec27c4ac0 (size 16): comm "Web Content", pid 5309, jiffies 4309675011 (age 68.076s) hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<0000000081f2894f>] nvkm_memory_tags_get+0x8...

...} for pidq16 comm="syz-executor330" path="/root/syz-executor330334897" dev="sda1" ino461 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1 executing program executing program BUG: memory leak unreferenced object 0xffff88812421fe40 (size 64): comm "syz-executor330", pid 7117, jiffies 4294949245 (age 13.030s) hex dump (first 32 bytes): 01 00 00 00 20 69 6f 63 00 00 00 00 64 65 76 2f .... ioc....dev/ 50 fe 21 24 81 88 ff ff 50 fe 21 24 81 88 ff ff P.!$....P.!$.... backtra...

...} for pidq16 comm="syz-executor330" path="/root/syz-executor330334897" dev="sda1" ino461 scontext=unconfined_u:system_r:insmod_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=1 executing program executing program BUG: memory leak unreferenced object 0xffff88812421fe40 (size 64): comm "syz-executor330", pid 7117, jiffies 4294949245 (age 13.030s) hex dump (first 32 bytes): 01 00 00 00 20 69 6f 63 00 00 00 00 64 65 76 2f .... ioc....dev/ 50 fe 21 24 81 88 ff ff 50 fe 21 24 81 88 ff ff P.!$....P.!$.... backtra...

...e-matching way more > trouble than you'd think. We're not interested in teaching the debugger > how to parse template instantiation names. > Having the template type parameter means we have an unambiguous > description of the type, and can match it easily. > > | including unreferenced entities fails source fidelity > I'll assume you meant to say _excluding_ unreferenced entities fails > source fidelity, > > Indeed > > which is quite true, but there is a valid engineering tradeoff in that > what the DWARF actually contains (or not, in the case of, say, un...

...e-matching way more > trouble than you'd think. We're not interested in teaching the debugger > how to parse template instantiation names. > Having the template type parameter means we have an unambiguous > description of the type, and can match it easily. > > | including unreferenced entities fails source fidelity > I'll assume you meant to say _excluding_ unreferenced entities fails > source fidelity, > > Indeed > > which is quite true, but there is a valid engineering tradeoff in that > what the DWARF actually contains (or not, in the case of, say, un...