search for: inbufs

https://bugzilla.samba.org/show_bug.cgi?id=9798 Summary: rsync crash with SIGSEGV when read time out happens Product: rsync Version: 3.0.2 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: vijunag at

https://bugzilla.samba.org/show_bug.cgi?id=5075 Summary: Syncing with --iconv may yield protocol error Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: lennart.samba@lovstrand.com

Hi All, I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there.

Hi All, I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there.

From: Hans de Goede <hdegoede at redhat.com> I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. virtio_console's port_fops_poll checks port->inbuf != NULL to determine if read won't block. However if an application reads enough bytes from

From: Hans de Goede <hdegoede at redhat.com> I found this while working on a Linux agent for spice, the symptom I was seeing was select blocking on the spice vdagent virtio serial port even though there were messages queued up there. virtio_console's port_fops_poll checks port->inbuf != NULL to determine if read won't block. However if an application reads enough bytes from

...rtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 kernel error: virtio-ports vport2p2: Error allocating inbufs qemu error: virtio-serial-bus: Guest failure in adding port 2 for device \ virtio-serial0.0 This happens because buffers for the in_vq are allocated when the port is added but are not released when the port is unplugged. They are only released when virtconsole is removed (s...

...rtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 (qemu) device_del serial0 (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ chardev=serial0,id=serial0,name=serial0 kernel error: virtio-ports vport2p2: Error allocating inbufs qemu error: virtio-serial-bus: Guest failure in adding port 2 for device \ virtio-serial0.0 This happens because buffers for the in_vq are allocated when the port is added but are not released when the port is unplugged. They are only released when virtconsole is removed (s...

I am not a member of the samba listserv, but I wanted to contribute the following code to the samba effort. The following is clipped from some experimental changes I have made to my own copy of the samba source. I have not included all of the changes because I don't have the time to. But someone should be able to properly do the integration without too much effort. Summary, these

Hi all, Thanks to Wayne and Park, I''ve got something like this now: static VALUE file_set_compressed(VALUE self, VALUE rbBool){ HANDLE h; BOOL rv; DWORD dwBytesReturned; int fn; USHORT inBuf = COMPRESSION_FORMAT_DEFAULT; if((rbBool != Qtrue) && (rbBool != Qfalse)){ rb_raise(rb_eTypeError,"Argument must be true or false"); }

...chardev=serial0,id=serial0,name=serial0 >> (qemu) device_del serial0 >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >> chardev=serial0,id=serial0,name=serial0 >> kernel error: >> virtio-ports vport2p2: Error allocating inbufs >> qemu error: >> virtio-serial-bus: Guest failure in adding port 2 for device \ >> virtio-serial0.0 >> >> This happens because buffers for the in_vq are allocated when the port is >> added but are not released when the port is unplugged. &...

...chardev=serial0,id=serial0,name=serial0 >> (qemu) device_del serial0 >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ >> chardev=serial0,id=serial0,name=serial0 >> kernel error: >> virtio-ports vport2p2: Error allocating inbufs >> qemu error: >> virtio-serial-bus: Guest failure in adding port 2 for device \ >> virtio-serial0.0 >> >> This happens because buffers for the in_vq are allocated when the port is >> added but are not released when the port is unplugged. &...

...0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > (qemu) device_del serial0 > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > kernel error: > virtio-ports vport2p2: Error allocating inbufs > qemu error: > virtio-serial-bus: Guest failure in adding port 2 for device \ > virtio-serial0.0 > > This happens because buffers for the in_vq are allocated when the port is > added but are not released when the port is unplugged. > > They are only...

...ial0,id=serial0,name=serial0 > >> (qemu) device_del serial0 > >> (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > >> chardev=serial0,id=serial0,name=serial0 > >> kernel error: > >> virtio-ports vport2p2: Error allocating inbufs > >> qemu error: > >> virtio-serial-bus: Guest failure in adding port 2 for device \ > >> virtio-serial0.0 > >> > >> This happens because buffers for the in_vq are allocated when the port is > >> added but are not released...

Hi, I've found a problem with samba when printing from a client running win95 + DFS. The print fails with a segmentation fault. The problem is that Win95 does not return the proper file_fsp( smb_vwv0) when doing an IOCTL request.This causes the file_fsp call in reply_ioctl (smbd/reply.c) to fail cause a segmentation fault. I do not understand how samba work, but here is my working patch

To make it complete, here is the code that I am using to encode a large file: int __stdcall SpxEncode(unsigned char* inBuf, unsigned char* outBuf, unsigned int inlen) { //char *testFile; //FILE *ftest; //testFile = "test"; //ftest = fopen(testFile, "wb"); //fwrite(inBuf,1,inlen,ftest); //take every 320 bytes //copy every short to float

https://bugzilla.samba.org/show_bug.cgi?id=11338 Bug ID: 11338 Summary: Rsync Crash - Segmentation fault Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Is it safe to change the inbuf[1025] to something larger... Like double it??? I understand this is just for my use- I'm not asking for a code base change. I have longer "variables" that I need to pass. Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL:

What do the messages below mean? I lost all network connectivity and started receiving these messages after changing username map from root = DELSOLW2K\Administrator to root = @"DELSOLW2K\Domain Admins". The system is Debian Sarge with Simo's latest debs and security = ADS. Using host libthread_db library "/lib/tls/libthread_db.so.1". `system-supplied DSO at

...0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > (qemu) device_del serial0 > (qemu) device_add virtserialport,bus=virtio-serial0.0,nr=2,\ > chardev=serial0,id=serial0,name=serial0 > kernel error: > virtio-ports vport2p2: Error allocating inbufs > qemu error: > virtio-serial-bus: Guest failure in adding port 2 for device \ > virtio-serial0.0 > > This happens because buffers for the in_vq are allocated when the port is > added but are not released when the port is unplugged. > > They are only...