similar to: [Bug 890] New: Bug in ulogd_filter_IP2BIN

http://bugzilla.netfilter.org/show_bug.cgi?id=741 Summary: ULOGD segfaults on init Product: ulogd Version: SVN (please provide timestamp) Platform: i386 OS/Version: other Status: NEW Severity: blocker Priority: P5 Component: ulogd_MYSQL AssignedTo: netfilter-buglog at lists.netfilter.org

https://bugzilla.netfilter.org/show_bug.cgi?id=1218 Bug ID: 1218 Summary: ULOGD PCAP Plugin Missing Ethernet Headers Product: ulogd Version: SVN (please provide timestamp) Hardware: All OS: All Status: NEW Severity: blocker Priority: P5 Component: ulogd Assignee:

Hi, I'm trying to use the samba4 registry tools for server-side editing of HKCU (ntuser.dat) on a Debian Etch samba 3 server. I was very pleased to see that backporting Debian experimental's samba4 package was very easy, so now I have a backported-to-Etch registry-tools package to start experiments : - regshell -F ntuser.dat works, one can manually add, remove, modify keys and

http://bugzilla.netfilter.org/show_bug.cgi?id=644 Summary: IP2BIN empty key prevents ulogd2 from starting Product: ulogd Version: SVN (please provide timestamp) Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: ulogd AssignedTo: netfilter-buglog at

This series introduces a generic readahead interface for btrfs trees. The intention is to use it to speed up scrub in a first run, but balance is another hot candidate. In general, every tree walk could be accompanied by a readahead. Deletion of large files comes to mind, where the fetching of the csums takes most of the time. Also the initial build-ups of free-space-caches and

Hi all, following the thread about the BTRFS_IOC_TREE_SEARCH ioctl [1], I made a patch which try to address the problem of restarting the ioctl. In the current solution is the application during the restart of the search to fill the min_* fields in the "struct btrfs_ioctl_search_key". In general the values set are the last one returned "+1". But doing so we reduce the

This series introduces a generic readahead interface for btrfs trees. The intention is to use it to speed up scrub in a first run, but balance is another hot candidate. In general, every tree walk could be accompanied by a readahead. Deletion of large files comes to mind, where the fetching of the csums takes most of the time. Also the initial build-ups of free-space-caches and

https://bugzilla.netfilter.org/show_bug.cgi?id=1193 Bug ID: 1193 Summary: Incorrect malloc for SQL statements and missing strings length check Product: ulogd Version: SVN (please provide timestamp) Hardware: All OS: All Status: NEW Severity: major Priority: P5

Hi, I was hoping I could modify a locally mounted registry hive using regpatch and a .reg file but the -F argument seems to have no function. (Strace shows it ignores it and just operates on /var/lib/samba/private/hklm.ldb) Below is output with debug on. rfm6 at ubuntuSSDx64:cp /mnt/xp/WINDOWS/system32/config/software /tmp/software rfm6 at ubuntuSSDx64:/tmp/config$ sudo regpatch -d=10 -F

Hi Linus, My for-linus branch has a one line fix: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus Sage hit a deadlock with ceph on btrfs, and Josef tracked it down to a regression in our initial rc1 pull. When doing nocow writes we were sometimes starting a transaction with locks held. Josef Bacik (1) commits (+1/-0): Btrfs: release path before starting

I''ve been working to try to improve the write-ahead log''s performance, and I found that the bottleneck addresses in the checksum items, especially when we want to make a random write on a large file, e.g a 4G file. Then a idea for this suggested by Chris is to use sub transaction ids and just to log the part of inode that had changed since either the last log commit or the last

Btrfs has always had these filler extent data items for holes in inodes. This has made somethings very easy, like logging hole punches and sending hole punches. However for large holey files these extent data items are pure overhead. So add an incompatible feature to no longer add hole extents to reduce the amount of metadata used by these sort of files. This has a few changes for logging and