search for: untestable

Hi, Can you give me some councils of remotely rebooting sip phones in asterisk server? How to configure sip_notify.conf and sip.conf? Kind regards, Guan ; Reboot Polycom Phone Event=>check-sync Content-Length=>0 ; Untested (Reboot Sipura Phone) Event=>resync Content-Length=>0 ; Untested (Reboot GrandStream Phone) Event=>sys-control ; Untested (Reboot Cisco Phone)

Fresh off the presses, completely untested... use at your own risk... -hpa -------------- next part -------------- A non-text attachment was scrubbed... Name: tmpfs-root.patch Type: text/x-patch Size: 1493 bytes Desc: not available Url : http://www.vas.nu/pipermail/klibc/attachments/20050404/dd420f06/tmpfs-root.bin

If I remove this code, diff --git a/tools/gold/gold-plugin.cpp b/tools/gold/gold-plugin.cpp index 46a5f46..a8978d5 100644 --- a/tools/gold/gold-plugin.cpp +++ b/tools/gold/gold-plugin.cpp @@ -428,8 +428,6 @@ getMinVisibility(GlobalValue::VisibilityTypes A, return A; if (B == GlobalValue::HiddenVisibility) return B; - if (A == GlobalValue::ProtectedVisibility) - return A;

Commit-ID: 850f98fa9ae27221b9086361251604e97a9eb686 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=850f98fa9ae27221b9086361251604e97a9eb686 Author: maximilian attems <max at stro.at> AuthorDate: Fri, 25 May 2012 20:15:20 +0200 Committer: maximilian attems <max at stro.at> CommitDate: Fri, 25 May 2012 20:21:07 +0200 [klibc] README update arch status alpha,

Thanks to work from Johnny, linux 3.18.12 with all the x4c blktap goodness have been built and are now in the virt6-testing repo. I've also uploaded libvirt 1.2.15. As you may have seen earlier today, virt6-testing also includes an updated 4.4.2 package with the latest security update (XSA-133). The kernel has had some basic testing (by myself, Johnny, and another community member), but

Seems to be largely untested... anyone using this? (cc'ing Kevin as he's the most likely candidate). At the least for MCAnalysis this appears to be unused, any ideas on what else can be deleted? I'll remove just this file unless there are objections tomorrow (or earlier if I get an ack from Kevin about it). -eric

On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > iovec addresses coming from vhost are assumed to be > pre-validated, but in fact can be speculated to a value > out of range. > > Userspace address are later validated with array_index_nospec so we can > be sure kernel info does not leak through these addresses, but vhost > must also not leak userspace info outside the allowed

On 2019/9/9 ??10:45, Michael S. Tsirkin wrote: > On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: >> On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: >>> iovec addresses coming from vhost are assumed to be >>> pre-validated, but in fact can be speculated to a value >>> out of range. >>> >>> Userspace address are later validated with

The attached patch attempts to implement Theora's cropping frame in Cortado. I make no claim that it is likely to work, as I have no clue how to build and test Jheora/Cortado. Please test. Thank you. I can at least confirm that CropImageFilter and FilteredImageSource were present in JDK 1.1. Performance impact in the absence of cropping should be negligible. With cropping, there might be

The two patches attached allow 9p filesystems to be mounted and listed. Note that I did *not* test the new list-9p function, because I don't have a guest with a new enough kernel handy. 9p filesystems are not included in the output of list-filesystems. Because a lot of existing code feeds the output of list-filesystems directly into the input of mount-options, mount-ro or (even worse) plain

.... Without this we might free a page (and have another user touch it) while the hypervisor is unprepared for it. But, if the bit is _not_ set, we are under no obligation to reverse the order. Furthermore, all modern qemus set this bit. So, the "tell second" code is completely unused and untestable. Quoting Anthony: "untested code is broken code". This _also_ means that we don't have to preserve a pfn list after the pages are freed, which should let us get rid of some temporary storage (vb->pfns) eventually. Signed-off-by: Dave Hansen <dave at linux.vnet.ibm.com> ---...

.... Without this we might free a page (and have another user touch it) while the hypervisor is unprepared for it. But, if the bit is _not_ set, we are under no obligation to reverse the order. Furthermore, all modern qemus set this bit. So, the "tell second" code is completely unused and untestable. Quoting Anthony: "untested code is broken code". This _also_ means that we don't have to preserve a pfn list after the pages are freed, which should let us get rid of some temporary storage (vb->pfns) eventually. Signed-off-by: Dave Hansen <dave at linux.vnet.ibm.com> ---...

On Tue, Sep 10, 2019 at 09:52:10AM +0800, Jason Wang wrote: > > On 2019/9/9 ??10:45, Michael S. Tsirkin wrote: > > On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: > > > On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > > > > iovec addresses coming from vhost are assumed to be > > > > pre-validated, but in fact can be speculated to a value

Hi all, I built my first asterisk using the traditional (?) .conf files and constructs. I recall reading books at the time about AEL but it seemed "new" and untested so I left it alone. Now, I'm interested to poll the audience here to see if I should look into using AEL instead (or in addition to) for future work. TIA

iovec addresses coming from vhost are assumed to be pre-validated, but in fact can be speculated to a value out of range. Userspace address are later validated with array_index_nospec so we can be sure kernel info does not leak through these addresses, but vhost must also not leak userspace info outside the allowed memory table to guests. Following the defence in depth principle, make sure the

iovec addresses coming from vhost are assumed to be pre-validated, but in fact can be speculated to a value out of range. Userspace address are later validated with array_index_nospec so we can be sure kernel info does not leak through these addresses, but vhost must also not leak userspace info outside the allowed memory table to guests. Following the defence in depth principle, make sure the

Random old patch that I had in my queue. Posting it as a backup, it is still untested. Rich.

> On Apr 19, 2018, at 1:22 PM, David Winsemius <dwinsemius at comcast.net> wrote: > > >> On Apr 19, 2018, at 11:20 AM, Ding, Yuan Chun <ycding at coh.org> wrote: >> >> Hi All, >> >> I want to create a categorical variable, cat.pfoa, in the file of pfas.pheno (a data frame) based on log2pfoa values. I can do it using the following code.

> As with Interix, I've recently added support for FreeBSD into > lib/System. Currently, the implementation of FreeBSD just uses the > "generic Unix" implementation which probably should work on FreeBSD. This fix problem. And more! Test result get improvment from last succesful build before (2004-08-29). Feature Test Results : Before: 112 tests total 85

On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: > > On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > > iovec addresses coming from vhost are assumed to be > > pre-validated, but in fact can be speculated to a value > > out of range. > > > > Userspace address are later validated with array_index_nospec so we can > > be sure kernel info does not