search for: dbufs

smbclient (and smbtar) in version 2.2.7a (and prior) has problems with large files (> 4GB). The following patch (against 2.2.7a) fixes all known problems with this. This code has been checked into the CVS tree in all branches as well. -- ====================================================================== Herb Lewis Silicon Graphics Networking Engineer

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

smbclient can create GNU tar files with long file names, but cannot restore them. The included patch will rectify this. This patch is against 1.9.18.p4. -Rob -- Rob Riggs Devil's Thumb Entertainment Network Administrator Boulder, CO - (303) 938-1200 rob@DevilsThumb.COM http://www.DevilsThumb.COM/~rob "The notion of errors is

Not all archs have the __io_virt() macro, so cirrus can't simply convert pointers that way. The drm format helpers have to use memcpy_toio() instead. This patch makes drm_fb_xrgb8888_to_rgb565_dstclip() accept a __iomem dst pointer and use memcpy_toio() instead of memcpy(). The helper function (drm_fb_xrgb8888_to_rgb565_line) has been changed to process a single scanline. Signed-off-by:

Not all archs have the __io_virt() macro, so cirrus can't simply convert pointers that way. The drm format helpers have to use memcpy_toio() instead. This patch makes drm_fb_xrgb8888_to_rgb888_dstclip() accept a __iomem dst pointer and use memcpy_toio() instead of memcpy(). The helper function (drm_fb_xrgb8888_to_rgb888_line) has been changed to process a single scanline. Signed-off-by:

Hi, Can a dbuf be in DB_CACHED state, db_holds == 0, b_efunc != NULL while its db_buf is put on the eviction list ? From an ASSERT in dbuf_do_evict(), it appears that it can. If it can, I am wondering what is preventing the following race dbuf_hold_impl() db = dbuf_find(dn, level, blkid); ... if (db->db_buf && refcount_is_zero(&db->db_holds)) {

..., I am wondering if anyone has seen this kernel panic before? It happened on an X4500 running Sol10U3 while it was receiving incremental snapshot updates. Thanks. Aug 25 17:01:50 ldasdata6 ^Mpanic[cpu0]/thread=fffffe857d53f7a0: Aug 25 17:01:50 ldasdata6 genunix: [ID 895785 kern.notice] dangling dbufs (dn=fffffe82a3532d10, dbuf=fffffe8b4e338b90) Aug 25 17:01:50 ldasdata6 unix: [ID 100000 kern.notice] Aug 25 17:01:50 ldasdata6 genunix: [ID 655072 kern.notice] fffffe8001112a80 zfs:zfsctl_ops_root+2fa59a42 () Aug 25 17:01:50 ldasdata6 genunix: [ID 655072 kern.notice] fffffe8001112ac0 zfs:dmu_objse...

The __io_virt() macro is not available on all architectures, so cirrus can't simply pass a pointer to io memory down to the format conversion helpers. The format conversion helpers must use memcpy_toio() instead. Add a convert_lines_toio() variant which does just that. Switch the drm_fb_*_dstclip() functions used by cirrus to accept a __iomem pointer as destination and pass that down to

Greetings, I am currently having a problem using smbclient (Samba v2.05a) running on Solaris 2.5.1 to restore a tar file from a tape drive onto a Win NT share. smbclient works successfully when using a tar file on disk, but is skipping the tar file (created by a third party) on the tape drive. The command used is as follows: smbclient //celeborn/test -U peter -T x /dev/rmt/0 The problem

Hi all, How''s this look? I based it on http://msdn.microsoft.com/en-us/library/aa366789(VS.85).aspx. I''m undecided as to when I should raise an error versus when I should just let it fall through, but this is how it is for now. You''ll need the latest windows-pr from CVS, btw. Regards, Dan PS - Where should I put it? In Windows::File directly? In a separate helper

On Mon, 2013-07-29 at 10:05 +0300, Michael S. Tsirkin wrote: > On Wed, Jul 24, 2013 at 08:31:34PM -0700, Sudeep Dutt wrote: > > From: Ashutosh Dixit <ashutosh.dixit at intel.com> > > > > This patch introduces the host "Virtio over PCIe" interface for > > Intel MIC. It allows creating user space backends on the host and > > instantiating virtio

On Mon, 2013-07-29 at 10:05 +0300, Michael S. Tsirkin wrote: > On Wed, Jul 24, 2013 at 08:31:34PM -0700, Sudeep Dutt wrote: > > From: Ashutosh Dixit <ashutosh.dixit at intel.com> > > > > This patch introduces the host "Virtio over PCIe" interface for > > Intel MIC. It allows creating user space backends on the host and > > instantiating virtio

Hi Christoph, On Wed, Aug 19, 2020 at 8:56 AM Christoph Hellwig <hch at lst.de> wrote: > > The V4L2-FLAG-MEMORY-NON-CONSISTENT flag is entirely unused, Could you explain what makes you think it's unused? It's a feature of the UAPI generally supported by the videobuf2 framework and relied on by Chromium OS to get any kind of reasonable performance when accessing V4L2 buffers

The V4L2-FLAG-MEMORY-NON-CONSISTENT flag is entirely unused, and causes weird gymanstics with the DMA_ATTR_NON_CONSISTENT flag, which is unimplemented except on PARISC and some MIPS configs, and about to be removed. Signed-off-by: Christoph Hellwig <hch at lst.de> --- .../userspace-api/media/v4l/buffer.rst | 17 --------- .../media/v4l/vidioc-reqbufs.rst | 1 -

Endianness issues are now consistent as per the documentation in host/mic_virtio.h. Note that the host can be both BE or LE whereas the card is always LE. Memory space sparse warnings are fixed for now by using __force. This is sufficient for now since the driver depends on x86 but will need to be revisited if we support other architectures which treat I/O memory differently from system memory.

Endianness issues are now consistent as per the documentation in host/mic_virtio.h. Note that the host can be both BE or LE whereas the card is always LE. Memory space sparse warnings are fixed for now by using __force. This is sufficient for now since the driver depends on x86 but will need to be revisited if we support other architectures which treat I/O memory differently from system memory.

Hi Tomasz, On 2020-08-19 12:16, Tomasz Figa wrote: > Hi Christoph, > > On Wed, Aug 19, 2020 at 8:56 AM Christoph Hellwig <hch at lst.de> wrote: >> >> The V4L2-FLAG-MEMORY-NON-CONSISTENT flag is entirely unused, > > Could you explain what makes you think it's unused? It's a feature of > the UAPI generally supported by the videobuf2 framework and relied

https://bugzilla.samba.org/show_bug.cgi?id=11215 Bug ID: 11215 Summary: compression/zlib errors discard the zlib error message Product: rsync Version: 3.1.0 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> zstd compression was announced as "good compression with high throughput" so I gave it a try. With zlib, on high speed links the CPU is usually the bottle neck. With zstd I'm able to fill a 200Mbit link :) zstd detection happens automatically via pkg-config. No zstd header means no error about missing zstd. So that

From: Ashutosh Dixit <ashutosh.dixit at intel.com> This patch introduces the host "Virtio over PCIe" interface for Intel MIC. It allows creating user space backends on the host and instantiating virtio devices for them on the Intel MIC card. A character device per MIC is exposed with IOCTL, mmap and poll callbacks. This allows the user space backend to: (a) add/remove a virtio