search for: init_size

...6.03. This is a regression caused by commit 8f470e7b movebits: Add syslinux_memmap_find() which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to the refactoring, prot_mode_size was passed as the length in the first call to syslinux_memmap_type(). After the refactoring, hdr.init_size was passed. Now, with commit ef81a3ad, one or the other is passed according to whether the kernel is relocatable. bios_boot_linux() reaches syslinux_shuffle_boot_rm(), rebooting if the kernel is relocatable and successfully starting the kernel if not. If I modify syslinux_memmap_find() to pass...

...* might not even be a Linux image, after all, and for !LOAD_HIGH + * we end up decompressing into a different location anyway), but + * if it is, make sure everything fits. + */ base = prot_mode_base; if (prot_mode_size && - syslinux_memmap_find(amap, &base, hdr.init_size, + syslinux_memmap_find(amap, &base, + hdr.relocatable_kernel ? + hdr.init_size : prot_mode_size, hdr.relocatable_kernel, hdr.kernel_alignment, - prot_mode_base, (addr_t)-1, - prot_mode_base, (addr_t)-1)) { + prot_mode_base, prot_mode_max, + pr...

"H. Peter Anvin" <hpa at zytor.com> on Tue, 2013/12/03 20:26: > On 10/24/2013 01:09 AM, Christian Hesse wrote: > >>> > >>> version 6.02-pre5 works, 6.02-pre6 does not. > >> > >> Struggled with git bisect, but finally succeeded: > >> > >> 8f470e7bfe75f6401f6c5432988c620b863ad274 is the first bad commit > >>

...ion caused by commit 8f470e7b > movebits: Add syslinux_memmap_find() > > which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to > the refactoring, prot_mode_size was passed as the length in the first call > to syslinux_memmap_type(). After the refactoring, hdr.init_size was > passed. Now, with commit ef81a3ad, one or the other is passed according to > whether the kernel is relocatable. > > bios_boot_linux() reaches syslinux_shuffle_boot_rm(), rebooting if the > kernel is relocatable and successfully starting the kernel if not. > > If I mo...

...bb0d..c466fb738de0 100644 --- a/arch/x86/boot/compressed/kaslr.c +++ b/arch/x86/boot/compressed/kaslr.c @@ -399,8 +399,6 @@ static void mem_avoid_init(unsigned long input, unsigned long input_size, */ mem_avoid[MEM_AVOID_ZO_RANGE].start = input; mem_avoid[MEM_AVOID_ZO_RANGE].size = (output + init_size) - input; - add_identity_map(mem_avoid[MEM_AVOID_ZO_RANGE].start, - mem_avoid[MEM_AVOID_ZO_RANGE].size); /* Avoid initrd. */ initrd_start = (u64)boot_params->ext_ramdisk_image << 32; @@ -420,14 +418,10 @@ static void mem_avoid_init(unsigned long input, unsigned long input_size,...

...from /lib/libc.so.6 No symbol table info available. #2 0x00007f9dd904d0db in str_vprintfa (str=0x11aa4f8, fmt=0x409184 "%u %s", args=0x7ffffab4fff0) at str.c:155 args2 = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffffab500e0, reg_save_area = 0x7ffffab50010}} init_size = 4231558 pos = 0 ret = <value optimized out> ret2 = <value optimized out> __FUNCTION__ = "str_vprintfa" #3 0x00000000004055ff in client_send_line (client=0x11d1e50, fmt=<value optimized out>) at pop3-client.c:678 str = 0x11aa4f8...

...malloc_unlocked () from /usr/lib/libc.so.1 > #5 0xff1c1ce0 in malloc () from /usr/lib/libc.so.1 > #6 0xff1b617c in calloc () from /usr/lib/libc.so.1 > #7 0x89c18 in pool_system_malloc (pool=0xb66f0, size=28) at mempool-system.c:67 > #8 0x7fa58 in buffer_create_dynamic (pool=0xb66f0, init_size=20) at buffer.c:109 > #9 0x56924 in index_transaction_init (t=0xcf090, ibox=0xd03a8, flags=0) at index-transaction.c:13 > #10 0x38fa0 in mbox_transaction_begin (box=0xcf090, flags=0) at mbox-transaction.c:16 > #11 0x71954 in mailbox_transaction_begin (box=0xcf090, flags=0) at mail-storage...

Hi, I've got report about issue when dovecot fails to start and there is no error logged (error goes only to stderr) situation: 1) dovecot is running 2) dovecot is automatically updated to new version (by yum update daemon), after update, dovecot is restarted (it's part of update script) 3) new dovecot fails to start (for whatever reason) result: dovecot not running and no error

Hey guys, got a question about the expire plugin. According to the wiki, the expire plugin "keeps an internal database (Berkeley DB or SQL)". I was wondering what fields in the mysql table are needed for expire to work. I assume it is setup is similar to the quota dict setup, so was just wondering what fields are required (i.e: select_field, where_field, username_field, for quota).

...7a95dd in p_malloc (buf=0x7f73ebdcef28, size=513) at > mempool.h:99 > No locals. > #6? buffer_alloc (buf=0x7f73ebdcef28, size=513) at buffer.c:34 > ??????? __func__ = "buffer_alloc" > #7? 0x00007f73f17a967b in buffer_create_dynamic (pool=<value optimized > out>, init_size=512) at buffer.c:143 > ??????? buf = 0x7f73ebdcef28 > #8? 0x00007f73f17a803b in backtrace_get (backtrace_r=0x7ffd0ddd8358) at > backtrace-string.c:86 > ??????? str = <value optimized out> > #9? 0x00007f73f17af1da in default_fatal_finish (type=<value optimized > out&gt...

On Wed, Jan 24, 2018 at 18:55:47 +0100, Thomas Robers wrote: > Am 23.01.2018 um 20:07 schrieb Josef 'Jeff' Sipek: > > On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote: > > > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: ... > > > 1. Do you have any idea what the imap process was doing at the time of the > > >

...mized out> #5 0x00007f73f17a95dd in p_malloc (buf=0x7f73ebdcef28, size=513) at mempool.h:99 No locals. #6 buffer_alloc (buf=0x7f73ebdcef28, size=513) at buffer.c:34 __func__ = "buffer_alloc" #7 0x00007f73f17a967b in buffer_create_dynamic (pool=<value optimized out>, init_size=512) at buffer.c:143 buf = 0x7f73ebdcef28 #8 0x00007f73f17a803b in backtrace_get (backtrace_r=0x7ffd0ddd8358) at backtrace-string.c:86 str = <value optimized out> #9 0x00007f73f17af1da in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:221...

...ea = 0x7ffd537d0b60, reg_save_area = 0x7ffd537d0aa0}} tmp = 0x1fe0e38 "proxy: Received invalid SSL certificate from \314-A\235q\210\021\b\354\062Lz?)\367.\002 \031\233 \362w?\224\356K7\343\224 \002\037\364!+\266\371\277O`K\021\b\315:6: k/CN=AddTrust External CA Root" init_size = 310 ret = <value optimized out> __FUNCTION__ = "t_noalloc_strdup_vprintf" #4 0x00007f1a58a221d9 in p_strdup_vprintf (pool=0x7f1a58c76830, format=<value optimized out>, args=<value optimized out>) at strfuncs.c:156 tmp = <value optimized...

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

Hi, here is the first public post of the patch-set to enable Linux to run under SEV-ES enabled hypervisors. The code is mostly feature-complete, but there are still a couple of bugs to fix. Nevertheless, given the size of the patch-set, I think it is about time to ask for initial feedback of the changes that come with it. To better understand the code here is a quick explanation of SEV-ES first.

From: Joerg Roedel <jroedel at suse.de> Hi, here is a rebased version of the latest SEV-ES patches. They are now based on latest tip/master instead of upstream Linux and include the necessary changes. Changes to v4 are in particular: - Moved early IDT setup code to idt.c, because the idt_descr and the idt_table are now static - This required to make stack protector work early (or

From: Joerg Roedel <jroedel at suse.de> Hi, here is the fourth version of the SEV-ES Guest Support patches. I addressed the review comments sent to me for the previous version and rebased the code v5.8-rc5. The biggest change in this version is the IST handling code for the #VC handler. I adapted the entry code for the #VC handler to the big pile of entry code changes merged into

From: Joerg Roedel <jroedel at suse.de> Hi, here is the fourth version of the SEV-ES Guest Support patches. I addressed the review comments sent to me for the previous version and rebased the code v5.8-rc5. The biggest change in this version is the IST handling code for the #VC handler. I adapted the entry code for the #VC handler to the big pile of entry code changes merged into

From: Joerg Roedel <jroedel at suse.de> Hi, here is the new version of the SEV-ES client enabling patch-set. It is based on the latest tip/master branch and contains the necessary changes. In particular those ar: - Enabling CR4.FSGSBASE early on supported processors so that early #VC exceptions on APs can be handled. - Add another patch (patch 1) to fix a KVM frame-size build

From: Joerg Roedel <jroedel at suse.de> Hi, here is a new version of the SEV-ES Guest Support patches for x86. The previous versions can be found as a linked list starting here: https://lore.kernel.org/lkml/20200824085511.7553-1-joro at 8bytes.org/ I updated the patch-set based on ther review comments I got and the discussions around it. Another important change is that the early IDT