search for: check_existing

We keep hitting bugs in the tree log replay because btrfs_remove_free_space doesn''t account for some corner case. So add a bunch of tests to try and fully test btrfs_remove_free_space since the only time it is called is during tree log replay. These tests all finish successfully, so as we find more of these bugs we need to add to these tests to make sure we don''t regress in

CID 1091471, Regression caused by 7c1de0038895cbc75ebd0caffc5b0f3f03c5ad51 This appears to be a typo which causes check_existence() to unconditionally return 1 in all cases. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> CC: Keir Frser <keir@xen.org> CC: Jan Beulich <jbeulich@suse.com> CC: Ian Campbell <ian.campbell@citrix.com> --- xen/drivers/char/ns16550.c |

If anybody is interested, which they are probably not, here is an improved and more rigorous version of mkcert.sh #! /bin/sh #*****************************************************************************# #| #| file : /root/apps/share/sh/create_dovecot_certificate #| #*---------------------------------------------------------------------------*# BELL="\007"

Besides single-port serial cards, also accept multi-port ones and such providing mixed functionality (e.g. also having a parallel port). Reading PCI_INTERRUPT_PIN before ACPI gets enabled generally produces an incorrect IRQ (below 16, whereas after enabling ACPI it frequently would end up at a higher one), so this is useful (almost) only when a system already boots in ACPI mode. Signed-off-by:

...he only message I got in my log file was this: imap(user at domain): Fatal: master: service(imap): child 6899 killed with signal 11 (core dumped) If I can help track this down, please let me know. Here's the backtrace: #0 hash_table_insert_node (table=0x10eff60, key=0x103, value=0x10fd8b0, check_existing=<value optimized out>) at hash.c:268 node = 0x69616d2d746e6573 prev = 0x10fbee0 hash = <value optimized out> __FUNCTION__ = "hash_table_insert_node" #1 0x00007fad738a11be in hash_table_insert (table=0x10eff60, key=0x1, value=0x101) at hash....

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. As before several of the patches are not to be applied because they can be done better using infrastructure from Julien''s "Allow Xen to boot with a raw Device Tree" patch. They are included for completeness. With

flight 19797 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/19797/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-winxpsp3-vcpus1 10 guest-saverestore.2 fail REGR. vs. 19794 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl 3 host-install(3) broken

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. With this rebase I''ve picked up some patches from Julien which were required to do things properly, so the gic v7 and device blacklisting patches have been changed to use the proper mechanisms. Previously I was able to boot

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have