search for: unplugg

...thing worked perfectly (upsmon, upssched, automatic shutdown etc.). When I connected computer back and tried to start powercom drivetr, I again got ups poweroff. Computer has 4 hdds - its load is >100Watt. But ups is still wired - even with empty batteries it shout work with any load until I unplugg it? Has anybody some other ideas? -- Wieslaw Kierbedz

...e I propose in this patch (PageOffline() + refcount == 0)? Simply skip over PageOffline pages. Reference count should never be != 0 at this stage. > In summary, is what you suggest simply delaying setting the reference count to 0 > in MEM_GOING_OFFLINE instead of right away when the driver unpluggs the pages? Yes > What's the big benefit you see and I fail to see? Aparat from no hooks into __put_page it is also an explicit control over the page via reference counting. Do you see any downsides? -- Michal Hocko SUSE Labs

...e I propose in this patch (PageOffline() + refcount == 0)? Simply skip over PageOffline pages. Reference count should never be != 0 at this stage. > In summary, is what you suggest simply delaying setting the reference count to 0 > in MEM_GOING_OFFLINE instead of right away when the driver unpluggs the pages? Yes > What's the big benefit you see and I fail to see? Aparat from no hooks into __put_page it is also an explicit control over the page via reference counting. Do you see any downsides? -- Michal Hocko SUSE Labs

...@ uint32_t fe_domid, be_domid = 0; libxl_device_disk disk = { 0 }; - if ((argc < 3) || (argc > 6)) { + if ((argc < 4) || (argc > 6)) { help("block-attach"); exit(0); } @@ -3489,7 +3489,7 @@ } disk.virtpath = argv[3]; disk.unpluggable = 1; - disk.readwrite = (argv[4][0] == ''w'') ? 1 : 0; + disk.readwrite = (argc <= 4 || argv[4][0] == ''w'') ? 1 : 0; if (domain_qualifier_to_domid(argv[1], &fe_domid, 0) < 0) { fprintf(stderr, "%s is an invalid domain identif...

Hello. I''ve built a kernel from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (Date: Fri Nov 19 19:46:45 2010 -0800) and got a kernel oops when tried to access to unplugged, but mounted external usb storage formatted with JFS. Steps to reproduce: mkfs.jfs /dev/sdb1 (unpluggable USB hard drive) mount /dev/sdb1 /mnt/drive cd /mnt/drive touch test sync ..unplug a drive ls Result: BUG: unable to handle kernel NULL pointer dereference at 000000...

...lugs the non-PV devices, which is undesirable in my application. I cannot arbitrarily change the kernel command line because it is in effect set by the user''s image. Therefore what I need to do is prevent Xen4 offering the facility to unplug the devices in the first place. Setting "(unpluggable 0)" in the config for the emulated NICs and disks does not appear to prevent them getting unplugged; what may be happening is that domU tries to unplug them (but fails) but still doesn''t use them. Is there a way to signal from dom0 that the kernel really shouldn''t unplug...

...gt; at this stage. Right, that should be guaranteed by d). (as long as people play by the rules) Same applies to my current patch. > >> In summary, is what you suggest simply delaying setting the reference count to 0 >> in MEM_GOING_OFFLINE instead of right away when the driver unpluggs the pages? > > Yes > >> What's the big benefit you see and I fail to see? > > Aparat from no hooks into __put_page it is also an explicit control over > the page via reference counting. Do you see any downsides? The only downside I see is that we get more false nega...

Package: logcheck Version: 1.2.63 Severity: minor Tags: patch Hi, There was recently a modification to filter acpid stuffs. But there are still things not filtered by logcheck. When I unplugg, then plug back my battery, I get following notifications: System Events =-=-=-=-=-=-= Nov 8 21:41:31 morpork acpid: received event "ac_adapter AC0 00000080 00000000" Nov 8 21:41:31 morpork acpid: completed event "ac_adapter AC0 00000080 00000000" Nov 8 21:41:31 morpork acp...

...current-operations (SRO): empty ( RO): false device ( RO): xvdb userdevice ( RW): xvdb bootable ( RW): false mode ( RW): RW type ( RW): Disk unpluggable ( RW): true currently-attached ( RO): false attachable ( RO): <expensive field> storage-lock ( RO): false status-code ( RO): 0 status-detail ( RO): qos_algorithm_type ( RW): qos_algorithm_params...

...T/xFEoA1 kFVog0ifUbR0/wXOyo159ItqqYxRhSq7Kz+abtA2tlogAQwUWsmdEWdQp5ALgCTR gcaZi/+TX/SCGB1OqkkdIKYBGprTheBl =4Dxi -----END PGP SIGNATURE----- [mod: There was a discussion between the (ex-) Linux-security moderators, Linus and a few others quite a while ago. The conclusion was that there were enough unpluggable holes in a chrooted environment that it didn''t pay to try to make it root-safe. If you want to find more of these holes, just look for the "suser()" call in your kernel sources, and try to think of a way to exploit that to get out of the "jail". A jail is not root-p...

...on. MEM_CANCEL_ONLINE is too late, because the range is already > unisolated again and the pages might be in use. > > For CMM it might not be that bad, because it can actually "reloan" any > pages. In contrast, virtio-mem cannot simply go ahead and reuse random > memory in unplugged. Any access to these pages would be evil. Giving them > back to the buddy is dangerous. Thanks, I was not aware of that code. But from what I understood this is an outright bug in this code because cmm_mem_going_offline releases pages to the buddy allocator which is something that is not reco...

...on. MEM_CANCEL_ONLINE is too late, because the range is already > unisolated again and the pages might be in use. > > For CMM it might not be that bad, because it can actually "reloan" any > pages. In contrast, virtio-mem cannot simply go ahead and reuse random > memory in unplugged. Any access to these pages would be evil. Giving them > back to the buddy is dangerous. Thanks, I was not aware of that code. But from what I understood this is an outright bug in this code because cmm_mem_going_offline releases pages to the buddy allocator which is something that is not reco...

...nt; + console_mfn : int64; +} + +type domid = int + +type disk_phystype = + | PHYSTYPE_QCOW + | PHYSTYPE_QCOW2 + | PHYSTYPE_VHD + | PHYSTYPE_AIO + | PHYSTYPE_FILE + | PHYSTYPE_PHY + +type disk_info = +{ + backend_domid : domid; + physpath : string; + phystype : disk_phystype; + virtpath : string; + unpluggable : bool; + readwrite : bool; + is_cdrom : bool; +} + +type nic_type = + | NICTYPE_IOEMU + | NICTYPE_VIF + +type nic_info = +{ + backend_domid : domid; + devid : int; + mtu : int; + model : string; + mac : int array; + bridge : string; + ifname : string; + script : string; + nictype : nic_type; +...

...NE is too late, because the range is already >> unisolated again and the pages might be in use. >> >> For CMM it might not be that bad, because it can actually "reloan" any >> pages. In contrast, virtio-mem cannot simply go ahead and reuse random >> memory in unplugged. Any access to these pages would be evil. Giving them >> back to the buddy is dangerous. > > Thanks, I was not aware of that code. But from what I understood this is > an outright bug in this code because cmm_mem_going_offline releases > pages to the buddy allocator which is so...

.../* this value is returned to the user: do not free right away */ - disk->virtpath = libxl_xs_read(ctx, XBT_NULL, libxl_sprintf(ctx, "%s/dev", backend)); + disk->virtpath = libxl_xs_read(&gc, XBT_NULL, libxl_sprintf(&gc, "%s/dev", backend)); disk->unpluggable = 1; disk->readwrite = 0; disk->is_cdrom = 1; free(path); + libxl_free_all(&gc); return 1; } static int libxl_destroy_device_model(libxl_ctx *ctx, uint32_t domid) { + libxl_gc gc = LIBXL_INIT_GC(ctx); char *pid; int ret; - pid = libxl_xs...

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before

...out a virtio-mem driver) won't be able to see/use this memory. The virtio-mem guest driver is needed to detect and manage these memory areas. What makes this memory special is that it can grow while the guest is running ("plug memory") and might shrink on a reboot (to compensate "unplugged" memory - see next paragraph). Each virtio-mem device manages exactly one such memory area. By having multiple ones assigned to different NUMA nodes, we can modify memory on a NUMA basis. Of course, we cannot shrink these memory areas while the guest is running. To be able to unplug memory,...

...out a virtio-mem driver) won't be able to see/use this memory. The virtio-mem guest driver is needed to detect and manage these memory areas. What makes this memory special is that it can grow while the guest is running ("plug memory") and might shrink on a reboot (to compensate "unplugged" memory - see next paragraph). Each virtio-mem device manages exactly one such memory area. By having multiple ones assigned to different NUMA nodes, we can modify memory on a NUMA basis. Of course, we cannot shrink these memory areas while the guest is running. To be able to unplug memory,...

...ver) won't be able to see/use > this memory. The virtio-mem guest driver is needed to detect and manage > these memory areas. What makes this memory special is that it can grow > while the guest is running ("plug memory") and might shrink on a reboot > (to compensate "unplugged" memory - see next paragraph). Each virtio-mem > device manages exactly one such memory area. By having multiple ones > assigned to different NUMA nodes, we can modify memory on a NUMA basis. > > Of course, we cannot shrink these memory areas while the guest is > running. To...

Hey, I thought there was supposed to be an ability for domU''s to be put into a hibernated state (E.g. current running tasks and memory) when dom0 is shutdown or rebooted. When I look in my /etc/default/xendomains file, I have the variable''s "XENDOMAINS_SAVE=/var/lib/xen/save" and "XENDOMAINS_RESTORE=true". However, when I reboot, I always have to restart my