search for: bufer

Hi Duncan, I've modified my backend such that the function isn't called anymore with iPTR. I still think that if iPTR is an invalid input to getValueTypeList() that the function should have at least an assert checking that. Thanks, Javier Hi Javier, > I've observed in some tests that getValueTypeList() is sometimes called > with type MVT::iPTR. I think this is a bug,

Hi Javier, > I’ve modified my backend such that the function isn’t called anymore > with iPTR. I still think that if iPTR is an invalid input to > getValueTypeList() that the function should have at least an assert > checking that. I agree - please post a patch adding one. Ciao, Duncan.

...AX_ALLOWED_VALUETYPE and LastSimpleValueType (inclusive) as this causes a buffer overrun. Thanks, Javier -----Original Message----- From: Duncan Sands [mailto:baldrick at free.fr] Sent: Tuesday, April 27, 2010 5:07 AM To: Martinez, Javier E Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] Bufer overrun in getValueTypeList() Hi Javier, > I've modified my backend such that the function isn't called anymore > with iPTR. I still think that if iPTR is an invalid input to > getValueTypeList() that the function should have at least an assert > checking that. I agree - plea...

Hello, I've observed in some tests that getValueTypeList() is sometimes called with type MVT::iPTR. There is a discrepancy between the size of the array VTs and the use in getTypeValueList(). The array is allocated with space for elements up to LAST_VALUE_TYPE and iPTR is defined after it. The enumerator value of iPTR is between LAST_VALUE_TYPE and LastSimpleValueType. For this reason the

...ite into the buffer. > > It looks like if another call then happens, and that > other call uses a different buffer, virtio rng > will happily return the data written into the > original buf pointer, confusing the caller. > > Is that right? > Yes. hw_random core uses two bufers: - rng_fillbuf that is used with a blocking access and protected by the reading_mutex. I think this cannot be interrupted by a kill because it's in hwrng_fillfn() and it's kthread. - rng_buffer that is used in rng_dev_read() and can be interrupted (it is also protected by reading_mutex)...

...ite into the buffer. > > It looks like if another call then happens, and that > other call uses a different buffer, virtio rng > will happily return the data written into the > original buf pointer, confusing the caller. > > Is that right? > Yes. hw_random core uses two bufers: - rng_fillbuf that is used with a blocking access and protected by the reading_mutex. I think this cannot be interrupted by a kill because it's in hwrng_fillfn() and it's kthread. - rng_buffer that is used in rng_dev_read() and can be interrupted (it is also protected by reading_mutex)...

...ram:buf, location of buffer to store data - * @param:buf_len, size of buffer - - * @out: src_ip, ip address of the data source - * @out: src_port, port number of the data source, host-byte order + * @param:socket, the open socket + * @param:data, data buffer to send + * @param:len, size of data bufer */ -int core_udp_recv(struct pxe_pvt_inode *socket, void *buf, uint16_t *buf_len, - uint32_t *src_ip, uint16_t *src_port) + +void core_udp_send(struct pxe_pvt_inode *socket, const void *data, size_t len) { - EFI_UDP4_COMPLETION_TOKEN token; - EFI_UDP4_FRAGMENT_DATA *frag; - EFI_UDP4_RE...

...and let me know the result. > http://people.freebsd.org/~yongari/re/if_re.c > http://people.freebsd.org/~yongari/re/if_rlreg.h > > > Ian > > > > -- > > Ian Freislich > > > > -- > Regards, > Pyun YongHyeon Pyun, I used it, and I got no bufer space available message, I run a server with heavey http requests and named as we.. so I had to increase the buffer. www# netstat -m 553/1862/2415 mbufs in use (current/cache/total) 279/1007/1286/65536 mbuf clusters in use (current/cache/total/max) 279/768 mbuf+clusters out of packet secondary zo...

...nother call then happens, and that > > other call uses a different buffer, virtio rng > > will happily return the data written into the > > original buf pointer, confusing the caller. > > > > Is that right? > > > > Yes. > > hw_random core uses two bufers: > > - rng_fillbuf that is used with a blocking access and protected by the > reading_mutex. I think this cannot be interrupted by a kill because it's > in hwrng_fillfn() and it's kthread. > > - rng_buffer that is used in rng_dev_read() and can be interrupted (it >...

The variable 'ok' is never used and generates a warning. Remove it. Also ntfssect.c is designed to be compiled in non Unicode mode when using MSVC compilers, so remove all ambiguity about it (LPCTSTR -> LPCSTR, use of 'A' API calls) so that it doesn't break when compiled in Unicode mode, which is what Rufus uses with MSVC. -------------- next part --------------

On 11/08/2020 14:53, Martin Wilck wrote: > On Tue, 2020-08-11 at 14:39 +0200, Laurent Vivier wrote: >> On 11/08/2020 14:22, Martin Wilck wrote: >>> On Tue, 2020-08-11 at 14:02 +0200, Laurent Vivier wrote: >>>>>> drivers/char/hw_random/virtio-rng.c | 14 ++++++++++++++ >>>>>> 1 file changed, 14 insertions(+) >>>>>>

On 11/08/2020 14:53, Martin Wilck wrote: > On Tue, 2020-08-11 at 14:39 +0200, Laurent Vivier wrote: >> On 11/08/2020 14:22, Martin Wilck wrote: >>> On Tue, 2020-08-11 at 14:02 +0200, Laurent Vivier wrote: >>>>>> drivers/char/hw_random/virtio-rng.c | 14 ++++++++++++++ >>>>>> 1 file changed, 14 insertions(+) >>>>>>

Hi, Is somewhere alghorithm description of encoder process implemented in libtheora? May be some drafts? May be frame dataflow throw encoder stages? PLEASE -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/theora/attachments/20110318/c3e8e109/attachment.htm

...fas.harvard.edu>wrote: > On 03/18/2011 01:44 PM, digital design wrote: > > Now i implement next stages of encoder^ > > Block1: > > 1) RGB->YUV > > 2) DCT of 16X16 blocks (pixel format 4:2:0) > > 3) zig-zag in eatch 8*8 block from previous step and push it to bufer > memory. > > > > i push 16X16 blocks to BLOCK1 using raster order (i'm right?) > > Now i'm confused - so much types of ordering. What i must do after DCT? > > What is order for pass blocks to Huffman block? > > In Theora terminology, a 16x16 unit spanning a...

On Sun, 2018-08-05 at 00:29 -0700, Christoph Hellwig wrote: > On Sun, Aug 05, 2018 at 11:10:15AM +1000, Benjamin Herrenschmidt wrote: > > - One you have rejected, which is to have a way for "no-iommu" virtio > > (which still doesn't use an iommu on the qemu side and doesn't need > > to), to be forced to use some custom DMA ops on the VM side. > > >

On Sun, 2018-08-05 at 00:29 -0700, Christoph Hellwig wrote: > On Sun, Aug 05, 2018 at 11:10:15AM +1000, Benjamin Herrenschmidt wrote: > > - One you have rejected, which is to have a way for "no-iommu" virtio > > (which still doesn't use an iommu on the qemu side and doesn't need > > to), to be forced to use some custom DMA ops on the VM side. > > >

...sentence means that the virtqueue buffer > > > starts with the header. > > > > > > For virtio-net mergable RX buffers the header is only in the first > > > buffer and the length field accounts for the entire fragmented packet > > > (that spans multiple bufers), so I suspected the specification was > > > needed here too. > > > > > > I'm happy to omit it. > > > > > \subsubsection{Device Events}\label{sec:Device Types / Socket Device / Device Operation / Device Events} > > > > > > > &g...

...sentence means that the virtqueue buffer > > > starts with the header. > > > > > > For virtio-net mergable RX buffers the header is only in the first > > > buffer and the length field accounts for the entire fragmented packet > > > (that spans multiple bufers), so I suspected the specification was > > > needed here too. > > > > > > I'm happy to omit it. > > > > > \subsubsection{Device Events}\label{sec:Device Types / Socket Device / Device Operation / Device Events} > > > > > > > &g...

...; > > > starts with the header. > > > > > > > > > > For virtio-net mergable RX buffers the header is only in the first > > > > > buffer and the length field accounts for the entire fragmented packet > > > > > (that spans multiple bufers), so I suspected the specification was > > > > > needed here too. > > > > > > > > > > I'm happy to omit it. > > > > > > > \subsubsection{Device Events}\label{sec:Device Types / Socket Device / Device Operation / Device Events}...

...esg-2.enc.z The log files are usually compressed using zlib. Users can see the log messages directly on the host or on the guest (using pstore filesystem). The 'directory' property is required for virtio-pstore device to work. It also adds 'bufsize' property to set size of pstore bufer. Cc: Paolo Bonzini <pbonzini at redhat.com> Cc: Radim Kr?m?? <rkrcmar at redhat.com> Cc: "Michael S. Tsirkin" <mst at redhat.com> Cc: Anthony Liguori <aliguori at amazon.com> Cc: Anton Vorontsov <anton at enomsg.org> Cc: Colin Cross <ccross at android.com...