UML kernel panic on initialization

UML kernel panic on initialization

[subashab]

Hi

I am seeing a panic on init when using Linux 5.13.1.
Following is the panic call stack-

Run /sbin/init as init process
init[1]: segfault at 0 ip 0000000040000af0 sp 0000007fbfb0be40 error 0 
in ld-2.13.so[40000000+20000]
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
CPU: 0 PID: 1 Comm: init Not tainted 5.13.1 #10
Stack:
  60462043 60462043 62037bc0 6202a000
  60537f9b 60462043 62045b01 6004191f
  62037bd0 6046f12c 62037cf0 60461d67
Call Trace:
  [<60462043>] ? printk+0x0/0x94
  [<600251ee>] show_stack+0x101/0x14e
  [<60462043>] ? printk+0x0/0x94
  [<60462043>] ? printk+0x0/0x94
  [<60462043>] ? printk+0x0/0x94
  [<6004191f>] ? exit_mm+0x0/0x2b0
  [<6046f12c>] dump_stack+0x34/0x36
  [<60461d67>] panic+0x18c/0x3d3
  [<60037322>] ? set_signals+0x28/0x40
  [<60461bdb>] ? panic+0x0/0x3d3
  [<60098bba>] ? acct_collect+0x0/0x1ff
  [<60037322>] ? set_signals+0x28/0x40
  [<6047651b>] ? _raw_spin_unlock_irq+0x1c/0x1e
  [<600372fa>] ? set_signals+0x0/0x40
  [<60037322>] ? set_signals+0x28/0x40
  [<6004aba1>] ? percpu_up_read.constprop.46+0x74/0x79
  [<6004ab2d>] ? percpu_up_read.constprop.46+0x0/0x79
  [<6004d59e>] ? exit_signals+0xa2/0x180
  [<6004191f>] ? exit_mm+0x0/0x2b0
  [<6004259c>] do_exit+0x27c/0x99a
  [<60043c8f>] do_group_exit+0x94/0x127
  [<6004e8e0>] get_signal+0x8cf/0x8fe
  [<60476406>] ? _raw_spin_lock_irq+0x0/0x2a
  [<6004dc20>] ? force_sig_info_to_task+0xd7/0xe9
  [<60024f9c>] do_signal+0x21/0x109
  [<6004e00f>] ? force_sig_fault+0x21/0x23
  [<600241ba>] interrupt_end+0x5c/0xc7
  [<6003a18c>] userspace+0x546/0x554
  [<6002415e>] ? interrupt_end+0x0/0xc7
  [<6003c6d5>] ? get_fp_registers+0x0/0x12
  [<60462043>] ? printk+0x0/0x94
  [<600223b8>] ? run_init_process+0xc2/0xca
  [<600223c0>] ? try_to_run_init_process+0x0/0x44
  [<600223d6>] ? try_to_run_init_process+0x16/0x44
  [<600223c0>] ? try_to_run_init_process+0x0/0x44
  [<60023ec6>] new_thread_handler+0xb0/0xb2
Aborted (core dumped)

After doing a git bisect, the first bad commit is listed as-

commit 84b2789d61156db0224724806b20110c0d34b07c
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Wed Jan 13 22:09:42 2021 +0100

     um: separate child and parent errors in clone stub

     If the two are mixed up, then it looks as though the parent
     returned an error if the child failed (before) the mmap(),
     and then the resulting process never gets killed. Fix this
     by splitting the child and parent errors, reporting and
     using them appropriately.

     Signed-off-by: Johannes Berg <johannes.berg@intel.com>
     Signed-off-by: Richard Weinberger <richard@nod.at>

I have reverted the following patches (to allow for a clean revert)
and I don't see the panic anymore -

bfc58e2b98e99737409cd9f4d86a79677c5b887c
dc01a3b9db43abf95b801c9694980777a329e303
9f0b4807a44ff81cf59421c8a86641efec586610
84b2789d61156db0224724806b20110c0d34b07c

Let me know if more information is needed to debug this.

The startup arguments I have been using are the following and is working 
upto Linux 5.11 -

./linux ubda=<full_path_to_rootfs> mem=512M 
eth0=daemon,00:18:8b:75:1d:e1

UML is compiled using the following arguments -

make -j32 linux ARCH=um SUBARCH=x86_64 CROSS_COMPILE=


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[YiFei Zhu]

On Sat, Jul 10, 2021 at 4:00 PM <subashab@codeaurora.org> wrote:
> Run /sbin/init as init process
> init[1]: segfault at 0 ip 0000000040000af0 sp 0000007fbfb0be40 error 0
> in ld-2.13.so[40000000+20000]

I haven't tried to reproduce this, but it looks like it failed in the
dynamic loader. Do you know what instruction it is failing at? It
should be at offset 1af0 in objdump -d `ld-2.13.so` assuming the first
instruction in objdump is 1000.

Could you also check if this instruction that is segfaulting is the
entry point address? If so, it could be that there's some sort of
failure in mapping the VMA, so if you could check the /proc/[pid]/maps
of the userspace traced process that would be great. You can identify
the traced process in that it has a different VSZ than the other UML
threads.

> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> CPU: 0 PID: 1 Comm: init Not tainted 5.13.1 #10
> Stack:
>   60462043 60462043 62037bc0 6202a000
>   60537f9b 60462043 62045b01 6004191f
>   62037bd0 6046f12c 62037cf0 60461d67
> Call Trace:
>   [<60462043>] ? printk+0x0/0x94
>   [<600251ee>] show_stack+0x101/0x14e
>   [<60462043>] ? printk+0x0/0x94
>   [<60462043>] ? printk+0x0/0x94
>   [<60462043>] ? printk+0x0/0x94
>   [<6004191f>] ? exit_mm+0x0/0x2b0
>   [<6046f12c>] dump_stack+0x34/0x36
>   [<60461d67>] panic+0x18c/0x3d3
>   [<60037322>] ? set_signals+0x28/0x40
>   [<60461bdb>] ? panic+0x0/0x3d3
>   [<60098bba>] ? acct_collect+0x0/0x1ff
>   [<60037322>] ? set_signals+0x28/0x40
>   [<6047651b>] ? _raw_spin_unlock_irq+0x1c/0x1e
>   [<600372fa>] ? set_signals+0x0/0x40
>   [<60037322>] ? set_signals+0x28/0x40
>   [<6004aba1>] ? percpu_up_read.constprop.46+0x74/0x79
>   [<6004ab2d>] ? percpu_up_read.constprop.46+0x0/0x79
>   [<6004d59e>] ? exit_signals+0xa2/0x180
>   [<6004191f>] ? exit_mm+0x0/0x2b0
>   [<6004259c>] do_exit+0x27c/0x99a
>   [<60043c8f>] do_group_exit+0x94/0x127
>   [<6004e8e0>] get_signal+0x8cf/0x8fe
>   [<60476406>] ? _raw_spin_lock_irq+0x0/0x2a
>   [<6004dc20>] ? force_sig_info_to_task+0xd7/0xe9
>   [<60024f9c>] do_signal+0x21/0x109
>   [<6004e00f>] ? force_sig_fault+0x21/0x23
>   [<600241ba>] interrupt_end+0x5c/0xc7
>   [<6003a18c>] userspace+0x546/0x554
>   [<6002415e>] ? interrupt_end+0x0/0xc7
>   [<6003c6d5>] ? get_fp_registers+0x0/0x12
>   [<60462043>] ? printk+0x0/0x94
>   [<600223b8>] ? run_init_process+0xc2/0xca
>   [<600223c0>] ? try_to_run_init_process+0x0/0x44
>   [<600223d6>] ? try_to_run_init_process+0x16/0x44
>   [<600223c0>] ? try_to_run_init_process+0x0/0x44
>   [<60023ec6>] new_thread_handler+0xb0/0xb2
> Aborted (core dumped)
>
> After doing a git bisect, the first bad commit is listed as-
>
> commit 84b2789d61156db0224724806b20110c0d34b07c
> Author: Johannes Berg <johannes.berg@intel.com>
> Date:   Wed Jan 13 22:09:42 2021 +0100
>
>      um: separate child and parent errors in clone stub
>
>      If the two are mixed up, then it looks as though the parent
>      returned an error if the child failed (before) the mmap(),
>      and then the resulting process never gets killed. Fix this
>      by splitting the child and parent errors, reporting and
>      using them appropriately.
>
>      Signed-off-by: Johannes Berg <johannes.berg@intel.com>
>      Signed-off-by: Richard Weinberger <richard@nod.at>
>
> I have reverted the following patches (to allow for a clean revert)
> and I don't see the panic anymore -
>
> bfc58e2b98e99737409cd9f4d86a79677c5b887c
> dc01a3b9db43abf95b801c9694980777a329e303
> 9f0b4807a44ff81cf59421c8a86641efec586610
> 84b2789d61156db0224724806b20110c0d34b07c
>
> Let me know if more information is needed to debug this.
>
> The startup arguments I have been using are the following and is working
> upto Linux 5.11 -
>
> ./linux ubda=<full_path_to_rootfs> mem=512M
> eth0=daemon,00:18:8b:75:1d:e1
>
> UML is compiled using the following arguments -
>
> make -j32 linux ARCH=um SUBARCH=x86_64 CROSS_COMPILE=
>
>
> _______________________________________________
> linux-um mailing list
> linux-um@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um

YiFei Zhu

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

On 2021-07-11 14:27, YiFei Zhu wrote:
> On Sat, Jul 10, 2021 at 4:00 PM <subashab@codeaurora.org> wrote:
>> Run /sbin/init as init process
>> init[1]: segfault at 0 ip 0000000040000af0 sp 0000007fbfb0be40 error 0
>> in ld-2.13.so[40000000+20000]
> 
> I haven't tried to reproduce this, but it looks like it failed in the
> dynamic loader. Do you know what instruction it is failing at? It
> should be at offset 1af0 in objdump -d `ld-2.13.so` assuming the first
> instruction in objdump is 1000.
> 
> Could you also check if this instruction that is segfaulting is the
> entry point address? If so, it could be that there's some sort of
> failure in mapping the VMA, so if you could check the /proc/[pid]/maps
> of the userspace traced process that would be great. You can identify
> the traced process in that it has a different VSZ than the other UML
> threads.
> 

The start of instructions is at af0 for me -

Disassembly of section .text:

0000000000000af0 <_dl_rtld_di_serinfo-0x7b10>:
      af0:       48 89 e7                mov    %rsp,%rdi

The offset at af0 from start is -

     15e0:       48 8d 35 79 97 01 00    lea    0x19779(%rip),%rsi        
# 1ad60 <calloc+0x56e0>

Here is the output of the /proc/[pid]/maps -

60000000-60719000 rwxp 00000000 103:00 12718929                          
<full_path_to_linux_binary>
60719000-6077b000 rwxp 00000000 00:00 0                                  
[heap]
6077b000-80000000 rwxs 0077b000 00:18 8                                  
/dev/shm/#8 (deleted)
80800000-80801000 rwxs 011f5000 00:18 8                                  
/dev/shm/#8 (deleted)
7ffff71d3000-7ffff71de000 r-xp 00000000 fd:00 131326                     
/lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff71de000-7ffff73dd000 ---p 0000b000 fd:00 131326                     
/lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff73dd000-7ffff73de000 r-xp 0000a000 fd:00 131326                     
/lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff73de000-7ffff73df000 rwxp 0000b000 fd:00 131326                     
/lib/x86_64-linux-gnu/libnss_files-2.23.so
7ffff73df000-7ffff73e5000 rwxp 00000000 00:00 0
7ffff73e5000-7ffff75a5000 r-xp 00000000 fd:00 131648                     
/lib/x86_64-linux-gnu/libc-2.23.so
7ffff75a5000-7ffff77a5000 ---p 001c0000 fd:00 131648                     
/lib/x86_64-linux-gnu/libc-2.23.so
7ffff77a5000-7ffff77a9000 r-xp 001c0000 fd:00 131648                     
/lib/x86_64-linux-gnu/libc-2.23.so
7ffff77a9000-7ffff77ab000 rwxp 001c4000 fd:00 131648                     
/lib/x86_64-linux-gnu/libc-2.23.so
7ffff77ab000-7ffff77af000 rwxp 00000000 00:00 0
7ffff77af000-7ffff77c7000 r-xp 00000000 fd:00 131033                     
/lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff77c7000-7ffff79c6000 ---p 00018000 fd:00 131033                     
/lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff79c6000-7ffff79c7000 r-xp 00017000 fd:00 131033                     
/lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff79c7000-7ffff79c8000 rwxp 00018000 fd:00 131033                     
/lib/x86_64-linux-gnu/libpthread-2.23.so
7ffff79c8000-7ffff79cc000 rwxp 00000000 00:00 0
7ffff79cc000-7ffff79d3000 r-xp 00000000 fd:00 130891                     
/lib/x86_64-linux-gnu/librt-2.23.so
7ffff79d3000-7ffff7bd2000 ---p 00007000 fd:00 130891                     
/lib/x86_64-linux-gnu/librt-2.23.so
7ffff7bd2000-7ffff7bd3000 r-xp 00006000 fd:00 130891                     
/lib/x86_64-linux-gnu/librt-2.23.so
7ffff7bd3000-7ffff7bd4000 rwxp 00007000 fd:00 130891                     
/lib/x86_64-linux-gnu/librt-2.23.so
7ffff7bd4000-7ffff7bd6000 r-xp 00000000 fd:00 131650                     
/lib/x86_64-linux-gnu/libutil-2.23.so
7ffff7bd6000-7ffff7dd5000 ---p 00002000 fd:00 131650                     
/lib/x86_64-linux-gnu/libutil-2.23.so
7ffff7dd5000-7ffff7dd6000 r-xp 00001000 fd:00 131650                     
/lib/x86_64-linux-gnu/libutil-2.23.so
7ffff7dd6000-7ffff7dd7000 rwxp 00002000 fd:00 131650                     
/lib/x86_64-linux-gnu/libutil-2.23.so
7ffff7dd7000-7ffff7dfd000 r-xp 00000000 fd:00 131032                     
/lib/x86_64-linux-gnu/ld-2.23.so
7ffff7fd6000-7ffff7fdb000 rwxp 00000000 00:00 0
7ffff7ff7000-7ffff7ffa000 r--p 00000000 00:00 0                          
[vvar]
7ffff7ffa000-7ffff7ffc000 r-xp 00000000 00:00 0                          
[vdso]
7ffff7ffc000-7ffff7ffd000 r-xp 00025000 fd:00 131032                     
/lib/x86_64-linux-gnu/ld-2.23.so
7ffff7ffd000-7ffff7ffe000 rwxp 00026000 fd:00 131032                     
/lib/x86_64-linux-gnu/ld-2.23.so
7ffff7ffe000-7ffff7fff000 rwxp 00000000 00:00 0
7ffffffde000-7ffffffff000 rwxp 00000000 00:00 0                          
[stack]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  
[vsyscall]

I don't know how to get VSZ from the maps output, so I used ps instead. 
The value is 536932.


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[YiFei Zhu]

On Mon, Jul 12, 2021 at 1:19 PM <subashab@codeaurora.org> wrote:
> The start of instructions is at af0 for me -
>
> Disassembly of section .text:
>
> 0000000000000af0 <_dl_rtld_di_serinfo-0x7b10>:
>       af0:       48 89 e7                mov    %rsp,%rdi
>
> The offset at af0 from start is -
>
>      15e0:       48 8d 35 79 97 01 00    lea    0x19779(%rip),%rsi
> # 1ad60 <calloc+0x56e0>

Interesting. I was expecting (from my ld-2.31.so) the initial ELF
header to be in an initial non-executable page, and .text to be in a
second page. Could you dump the segment headers with `readelf -lW
ld-2.13.so`?

Though, considering that:
* the address of the start of .text matches exactly with the expected
offset from the page where the faulting instruction is (40000af0)
* UML doesn't have ASLR so 40000000 is probably where the loader is
mapped into memory
* my ld-2.31.so has its entry point address as 0x1100 and that is also
the start of .text (PLT/GOT precedes it hence the 0x100 offset from
page start)
I'm pretty confident that 40000af0 was the entry point of the dynamic
loader after it's mapped into memory (with the ELF entry point address
as 0xaf0, you can check with `readelf -h ld-2.13.so`).

If that is the case, then this faulting instruction is the first
instruction executed in UML userspace, and the instruction is `mov
%rsp,%rdi`. This instruction should not normally fail. The only common
reason I can think of is the userspace's page isn't mapped properly
somehow; either it's not mapped at all or it's not mapped executable.

> Here is the output of the /proc/[pid]/maps -
>
> 60000000-60719000 rwxp 00000000 103:00 12718929
> <full_path_to_linux_binary>
> 60719000-6077b000 rwxp 00000000 00:00 0
> [heap]

Uhh... this is a UML kernel process. UML clones into many threads /
processes, and each userspace task (inside UML) is a separate UML
userspace process on the host (so as to isolate their address spaces,
hence different VSZ from kernel). The UML userspace processes should
not map the UML binary on the host, but rather lots and lots of
/dev/shm/#8 maps (/dev/shm/#8 is UML's "physical memory").

Since UML userspace dies almost immediately due to the segfault, you
probably want to stop it from being killed by UML kernel upon segfault
so you have a longer time window to look at the maps. What I would
probably do is to add an infinite loop where the kernel printk the
segfault information, in arch/um/kernel/trap.c, show_segv_info.

> I don't know how to get VSZ from the maps output, so I used ps instead.
> The value is 536932.
>

By the way, I compiled UML 5.13.1 with defconfig, with

  make -j4 ARCH=um SUBARCH=x86_64 CROSS_COMPILE=

and

  ./linux mem=512M root=none rootfstype=hostfs rootflags=/ ro
console=tty init=/bin/sh

Cannot reproduce this error. To make sure it's not related to config,
does the panic still occur if you use defconfig?

YiFei Zhu

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Anton Ivanov]

On 13/07/2021 05:04, YiFei Zhu wrote:
> On Mon, Jul 12, 2021 at 1:19 PM <subashab@codeaurora.org> wrote:
>> The start of instructions is at af0 for me -
>>
>> Disassembly of section .text:
>>
>> 0000000000000af0 <_dl_rtld_di_serinfo-0x7b10>:
>>        af0:       48 89 e7                mov    %rsp,%rdi
>>
>> The offset at af0 from start is -
>>
>>       15e0:       48 8d 35 79 97 01 00    lea    0x19779(%rip),%rsi
>> # 1ad60 <calloc+0x56e0>
> Interesting. I was expecting (from my ld-2.31.so) the initial ELF
> header to be in an initial non-executable page, and .text to be in a
> second page. Could you dump the segment headers with `readelf -lW
> ld-2.13.so`?
>
> Though, considering that:
> * the address of the start of .text matches exactly with the expected
> offset from the page where the faulting instruction is (40000af0)
> * UML doesn't have ASLR so 40000000 is probably where the loader is
> mapped into memory
> * my ld-2.31.so has its entry point address as 0x1100 and that is also
> the start of .text (PLT/GOT precedes it hence the 0x100 offset from
> page start)
> I'm pretty confident that 40000af0 was the entry point of the dynamic
> loader after it's mapped into memory (with the ELF entry point address
> as 0xaf0, you can check with `readelf -h ld-2.13.so`).
>
> If that is the case, then this faulting instruction is the first
> instruction executed in UML userspace, and the instruction is `mov
> %rsp,%rdi`. This instruction should not normally fail. The only common
> reason I can think of is the userspace's page isn't mapped properly
> somehow; either it's not mapped at all or it's not mapped executable.
>
>> Here is the output of the /proc/[pid]/maps -
>>
>> 60000000-60719000 rwxp 00000000 103:00 12718929
>> <full_path_to_linux_binary>
>> 60719000-6077b000 rwxp 00000000 00:00 0
>> [heap]
> Uhh... this is a UML kernel process. UML clones into many threads /
> processes, and each userspace task (inside UML) is a separate UML
> userspace process on the host (so as to isolate their address spaces,
> hence different VSZ from kernel). The UML userspace processes should
> not map the UML binary on the host, but rather lots and lots of
> /dev/shm/#8 maps (/dev/shm/#8 is UML's "physical memory").
>
> Since UML userspace dies almost immediately due to the segfault, you
> probably want to stop it from being killed by UML kernel upon segfault
> so you have a longer time window to look at the maps. What I would
> probably do is to add an infinite loop where the kernel printk the
> segfault information, in arch/um/kernel/trap.c, show_segv_info.
>
>> I don't know how to get VSZ from the maps output, so I used ps instead.
>> The value is 536932.
>>
> By the way, I compiled UML 5.13.1 with defconfig, with
>
>    make -j4 ARCH=um SUBARCH=x86_64 CROSS_COMPILE=
>
> and
>
>    ./linux mem=512M root=none rootfstype=hostfs rootflags=/ ro
> console=tty init=/bin/sh
>
> Cannot reproduce this error. To make sure it's not related to config,
> does the panic still occur if you use defconfig?

Same here. I cannot reproduce the error. I use the debian config for 64 with vde disabled for most of my tests.

Can we have your .config please?

A.

>
> YiFei Zhu
>
-- 
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Richard Weinberger]

----- Ursprüngliche Mail -----
>>    ./linux mem=512M root=none rootfstype=hostfs rootflags=/ ro
>> console=tty init=/bin/sh
>>
>> Cannot reproduce this error. To make sure it's not related to config,
>> does the panic still occur if you use defconfig?
> 
> Same here. I cannot reproduce the error. I use the debian config for 64 with vde
> disabled for most of my tests.
> 
> Can we have your .config please?

If possible, please share your userspace. Maybe the ld.so you're using is
special and triggers the bug.

Thanks,
//richard

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

>> Cannot reproduce this error. To make sure it's not related to config,
>> does the panic still occur if you use defconfig?
> 
> Same here. I cannot reproduce the error. I use the debian config for
> 64 with vde disabled for most of my tests.
> 
> Can we have your .config please?
> 

Sure, I have attached it here.

[-- Attachment #2: .config --]
[-- Type: text/plain, Size: 34652 bytes --]

#
# Automatically generated file; DO NOT EDIT.
# Linux/um 5.13.0 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609"
CONFIG_CC_IS_GCC=y
CONFIG_GCC_VERSION=50400
CONFIG_CLANG_VERSION=0
CONFIG_AS_IS_GNU=y
CONFIG_AS_VERSION=22601
CONFIG_LD_IS_BFD=y
CONFIG_LD_VERSION=22601
CONFIG_LLD_VERSION=0
CONFIG_CC_CAN_LINK=y
CONFIG_CC_CAN_LINK_STATIC=y
CONFIG_CC_HAS_ASM_GOTO=y
CONFIG_IRQ_WORK=y

#
# General setup
#
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=128
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_BUILD_SALT=""
CONFIG_DEFAULT_INIT=""
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
# CONFIG_WATCH_QUEUE is not set
CONFIG_CROSS_MEMORY_ATTACH=y
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_SHOW=y
# end of IRQ subsystem

CONFIG_GENERIC_CLOCKEVENTS=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
# end of Timers subsystem

CONFIG_BPF=y

#
# BPF subsystem
#
# CONFIG_BPF_SYSCALL is not set
# end of BPF subsystem

CONFIG_PREEMPT_NONE=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_TASKSTATS is not set
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting

#
# RCU Subsystem
#
CONFIG_TINY_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
CONFIG_TINY_SRCU=y
# end of RCU Subsystem

CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_IKHEADERS is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13

#
# Scheduler features
#
# end of Scheduler features

CONFIG_CC_HAS_INT128=y
CONFIG_CGROUPS=y
# CONFIG_MEMCG is not set
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
# CONFIG_CGROUP_RDMA is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_MISC is not set
# CONFIG_CGROUP_DEBUG is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_NET_NS=y
# CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_SCHED_AUTOGROUP is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_BOOT_CONFIG is not set
# CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_SYSCTL=y
CONFIG_HAVE_UID16=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SYSFS_SYSCALL=y
CONFIG_FHANDLE=y
CONFIG_POSIX_TIMERS=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_FUTEX_PI=y
CONFIG_HAVE_FUTEX_CMPXCHG=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_IO_URING=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
# CONFIG_USERFAULTFD is not set
# CONFIG_EMBEDDED is not set

#
# Kernel Performance Events And Counters
#
# end of Kernel Performance Events And Counters

CONFIG_VM_EVENT_COUNTERS=y
CONFIG_COMPAT_BRK=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
CONFIG_SLAB_MERGE_DEFAULT=y
# CONFIG_SLAB_FREELIST_RANDOM is not set
# CONFIG_SLAB_FREELIST_HARDENED is not set
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not set
# CONFIG_PROFILING is not set
# end of General setup

#
# UML-specific options
#
CONFIG_UML=y
CONFIG_MMU=y
CONFIG_NO_IOMEM=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_HZ=100
CONFIG_NR_CPUS=1

#
# Host processor type and features
#
# CONFIG_MK8 is not set
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
CONFIG_GENERIC_CPU=y
CONFIG_X86_INTERNODE_CACHE_SHIFT=6
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_IA32_FEAT_CTL=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_HYGON=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_CPU_SUP_ZHAOXIN=y
# end of Host processor type and features

CONFIG_UML_X86=y
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_3_LEVEL_PGTABLES=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_STATIC_LINK is not set
CONFIG_LD_SCRIPT_DYN=y
CONFIG_HOSTFS=y
CONFIG_MCONSOLE=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_KERNEL_STACK_ORDER=2
# CONFIG_MMAPPER is not set
CONFIG_PGTABLE_LEVELS=3
# CONFIG_UML_TIME_TRAVEL_SUPPORT is not set
# end of UML-specific options

#
# UML Character Devices
#
CONFIG_STDERR_CONSOLE=y
CONFIG_SSL=y
CONFIG_NULL_CHAN=y
CONFIG_PORT_CHAN=y
CONFIG_PTY_CHAN=y
CONFIG_TTY_CHAN=y
CONFIG_XTERM_CHAN=y
CONFIG_CON_ZERO_CHAN="fd:0,fd:1"
CONFIG_CON_CHAN="pts"
CONFIG_SSL_CHAN="pts"
CONFIG_UML_SOUND=m
CONFIG_SOUND=m
CONFIG_SOUND_OSS_CORE=y
CONFIG_HOSTAUDIO=m
# end of UML Character Devices

#
# UML Network Devices
#
CONFIG_UML_NET=y
CONFIG_UML_NET_ETHERTAP=y
CONFIG_UML_NET_TUNTAP=y
CONFIG_UML_NET_SLIP=y
CONFIG_UML_NET_DAEMON=y
# CONFIG_UML_NET_VECTOR is not set
# CONFIG_UML_NET_VDE is not set
CONFIG_UML_NET_MCAST=y
# CONFIG_UML_NET_PCAP is not set
CONFIG_UML_NET_SLIRP=y
# end of UML Network Devices

# CONFIG_VIRTIO_UML is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
CONFIG_PM_SLEEP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set

#
# General architecture-dependent options
#
CONFIG_CRASH_CORE=y
CONFIG_SET_FS=y
CONFIG_HAVE_64BIT_ALIGNED_ACCESS=y
CONFIG_HAVE_ASM_MODVERSIONS=y
CONFIG_HAVE_ARCH_SECCOMP=y
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y
# CONFIG_SECCOMP_CACHE_DEBUG is not set
CONFIG_LTO_NONE=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_MODULES_USE_ELF_RELA=y
# CONFIG_COMPAT_32BIT_TIME is not set
CONFIG_ARCH_NO_PREEMPT=y
CONFIG_ARCH_EPHEMERAL_INODES=y

#
# GCOV-based kernel profiling
#
# end of GCOV-based kernel profiling

CONFIG_HAVE_GCC_PLUGINS=y
# end of General architecture-dependent options

CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
# CONFIG_MODULE_SIG is not set
CONFIG_MODULE_COMPRESS_NONE=y
# CONFIG_MODULE_COMPRESS_GZIP is not set
# CONFIG_MODULE_COMPRESS_XZ is not set
# CONFIG_MODULE_COMPRESS_ZSTD is not set
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set
CONFIG_MODPROBE_PATH="/sbin/modprobe"
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_BSGLIB is not set
# CONFIG_BLK_DEV_INTEGRITY is not set
# CONFIG_BLK_DEV_ZONED is not set
# CONFIG_BLK_DEV_THROTTLING is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
# CONFIG_BLK_WBT is not set
# CONFIG_BLK_CGROUP_IOLATENCY is not set
# CONFIG_BLK_CGROUP_IOCOST is not set
# CONFIG_BLK_CGROUP_IOPRIO is not set
# CONFIG_BLK_SED_OPAL is not set
# CONFIG_BLK_INLINE_ENCRYPTION is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
# end of Partition Types

CONFIG_BLK_PM=y

#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
CONFIG_MQ_IOSCHED_DEADLINE_CGROUP=y
CONFIG_MQ_IOSCHED_KYBER=y
CONFIG_IOSCHED_BFQ=m
# CONFIG_BFQ_GROUP_IOSCHED is not set
# end of IO Schedulers

CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
CONFIG_INLINE_WRITE_UNLOCK=y
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_FREEZER=y

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
CONFIG_BINFMT_MISC=m
CONFIG_COREDUMP=y
# end of Executable file formats

#
# Memory Management options
#
CONFIG_FLATMEM=y
CONFIG_SPLIT_PTLOCK_CPUS=4
# CONFIG_COMPACTION is not set
# CONFIG_PAGE_REPORTING is not set
CONFIG_PHYS_ADDR_T_64BIT=y
# CONFIG_KSM is not set
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
CONFIG_NEED_PER_CPU_KM=y
# CONFIG_CLEANCACHE is not set
# CONFIG_FRONTSWAP is not set
# CONFIG_CMA is not set
# CONFIG_ZPOOL is not set
# CONFIG_ZBUD is not set
# CONFIG_ZSMALLOC is not set
# CONFIG_IDLE_PAGE_TRACKING is not set
# CONFIG_PERCPU_STATS is not set

#
# GUP_TEST needs to have DEBUG_FS enabled
#
# end of Memory Management options

CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_DIAG is not set
CONFIG_UNIX=y
CONFIG_UNIX_SCM=y
# CONFIG_UNIX_DIAG is not set
# CONFIG_TLS is not set
# CONFIG_XFRM_USER is not set
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE_DEMUX is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_NET_IPVTI is not set
# CONFIG_NET_FOU is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_INET_UDP_DIAG is not set
# CONFIG_INET_RAW_DIAG is not set
# CONFIG_INET_DIAG_DESTROY is not set
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_MPTCP is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
# CONFIG_NETFILTER is not set
# CONFIG_BPFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_L2TP is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
# CONFIG_NET_SCHED is not set
# CONFIG_DCB is not set
# CONFIG_BATMAN_ADV is not set
# CONFIG_OPENVSWITCH is not set
# CONFIG_VSOCKETS is not set
# CONFIG_NETLINK_DIAG is not set
# CONFIG_MPLS is not set
# CONFIG_NET_NSH is not set
# CONFIG_HSR is not set
# CONFIG_NET_SWITCHDEV is not set
# CONFIG_NET_L3_MASTER_DEV is not set
# CONFIG_QRTR is not set
# CONFIG_NET_NCSI is not set
# CONFIG_CGROUP_NET_PRIO is not set
# CONFIG_CGROUP_NET_CLASSID is not set
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# end of Network testing
# end of Networking options

# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_AF_KCM is not set
CONFIG_WIRELESS=y
# CONFIG_CFG80211 is not set

#
# CFG80211 needs to be enabled for MAC80211
#
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set
# CONFIG_PSAMPLE is not set
# CONFIG_NET_IFE is not set
# CONFIG_LWTUNNEL is not set
# CONFIG_FAILOVER is not set
CONFIG_ETHTOOL_NETLINK=y

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_UEVENT_HELPER is not set
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y

#
# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE=""
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_FW_LOADER_COMPRESS is not set
CONFIG_FW_CACHE=y
# end of Firmware loader

CONFIG_ALLOW_DEV_COREDUMP=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not set
CONFIG_GENERIC_CPU_DEVICES=y
# end of Generic Driver Options

#
# Bus devices
#
# CONFIG_MHI_BUS is not set
# end of Bus devices

# CONFIG_CONNECTOR is not set
# CONFIG_GNSS is not set
# CONFIG_MTD is not set
# CONFIG_OF is not set
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_NULL_BLK is not set
CONFIG_BLK_DEV_UBD=y
# CONFIG_BLK_DEV_UBD_SYNC is not set
CONFIG_BLK_DEV_COW_COMMON=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_RBD is not set

#
# NVME Support
#
# CONFIG_NVME_TCP is not set
# end of NVME Support

#
# Misc devices
#
# CONFIG_DUMMY_IRQ is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_C2PORT is not set

#
# EEPROM support
#
# CONFIG_EEPROM_93CX6 is not set
# end of EEPROM support

#
# Texas Instruments shared transport line discipline
#
# end of Texas Instruments shared transport line discipline

#
# Altera FPGA firmware download module (requires I2C)
#
# CONFIG_ECHO is not set
# CONFIG_PVPANIC is not set
# end of Misc devices

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# end of SCSI device support

# CONFIG_MD is not set
# CONFIG_TARGET_CORE is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
CONFIG_DUMMY=m
# CONFIG_WIREGUARD is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_TEAM is not set
# CONFIG_MACVLAN is not set
# CONFIG_IPVLAN is not set
# CONFIG_VXLAN is not set
# CONFIG_GENEVE is not set
# CONFIG_BAREUDP is not set
# CONFIG_GTP is not set
# CONFIG_MACSEC is not set
# CONFIG_NETCONSOLE is not set
CONFIG_TUN=m
# CONFIG_TUN_VNET_CROSS_LE is not set
# CONFIG_VETH is not set
# CONFIG_NLMON is not set
CONFIG_ETHERNET=y
CONFIG_NET_VENDOR_ALACRITECH=y
CONFIG_NET_VENDOR_AMAZON=y
CONFIG_NET_VENDOR_AQUANTIA=y
CONFIG_NET_VENDOR_ARC=y
CONFIG_NET_VENDOR_CAVIUM=y
CONFIG_NET_VENDOR_CORTINA=y
CONFIG_NET_VENDOR_EZCHIP=y
CONFIG_NET_VENDOR_GOOGLE=y
CONFIG_NET_VENDOR_HUAWEI=y
CONFIG_NET_VENDOR_I825XX=y
CONFIG_NET_VENDOR_INTEL=y
CONFIG_NET_VENDOR_MICROSOFT=y
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_NET_VENDOR_MICROCHIP=y
CONFIG_NET_VENDOR_MICROSEMI=y
CONFIG_NET_VENDOR_NATSEMI=y
CONFIG_NET_VENDOR_NETRONOME=y
CONFIG_NET_VENDOR_NI=y
CONFIG_NET_VENDOR_8390=y
CONFIG_NET_VENDOR_PENSANDO=y
CONFIG_NET_VENDOR_QUALCOMM=y
# CONFIG_RMNET is not set
CONFIG_NET_VENDOR_RENESAS=y
CONFIG_NET_VENDOR_ROCKER=y
CONFIG_NET_VENDOR_SAMSUNG=y
CONFIG_NET_VENDOR_SOLARFLARE=y
CONFIG_NET_VENDOR_SOCIONEXT=y
CONFIG_NET_VENDOR_SYNOPSYS=y
CONFIG_NET_VENDOR_VIA=y
CONFIG_NET_VENDOR_XILINX=y
# CONFIG_PHYLIB is not set
# CONFIG_MDIO_DEVICE is not set

#
# PCS device drivers
#
# end of PCS device drivers

CONFIG_PPP=m
# CONFIG_PPP_BSDCOMP is not set
# CONFIG_PPP_DEFLATE is not set
# CONFIG_PPP_FILTER is not set
# CONFIG_PPP_MPPE is not set
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPPOE is not set
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
CONFIG_SLIP=m
CONFIG_SLHC=m
# CONFIG_SLIP_COMPRESSED is not set
# CONFIG_SLIP_SMART is not set
# CONFIG_SLIP_MODE_SLIP6 is not set

#
# Host-side USB support is needed for USB Network Adapter support
#
CONFIG_WLAN=y
CONFIG_WLAN_VENDOR_ADMTEK=y
CONFIG_WLAN_VENDOR_ATH=y
# CONFIG_ATH_DEBUG is not set
CONFIG_WLAN_VENDOR_ATMEL=y
CONFIG_WLAN_VENDOR_BROADCOM=y
CONFIG_WLAN_VENDOR_CISCO=y
CONFIG_WLAN_VENDOR_INTEL=y
CONFIG_WLAN_VENDOR_INTERSIL=y
# CONFIG_HOSTAP is not set
CONFIG_WLAN_VENDOR_MARVELL=y
CONFIG_WLAN_VENDOR_MEDIATEK=y
CONFIG_WLAN_VENDOR_MICROCHIP=y
CONFIG_WLAN_VENDOR_RALINK=y
CONFIG_WLAN_VENDOR_REALTEK=y
CONFIG_WLAN_VENDOR_RSI=y
CONFIG_WLAN_VENDOR_ST=y
CONFIG_WLAN_VENDOR_TI=y
CONFIG_WLAN_VENDOR_ZYDAS=y
CONFIG_WLAN_VENDOR_QUANTENNA=y
# CONFIG_WAN is not set

#
# Wireless WAN
#
# CONFIG_WWAN is not set
# end of Wireless WAN

# CONFIG_NET_FAILOVER is not set
# CONFIG_NVM is not set

#
# Character devices
#
CONFIG_TTY=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=32
CONFIG_LDISC_AUTOLOAD=y
# CONFIG_N_GSM is not set
# CONFIG_NULL_TTY is not set
# CONFIG_SERIAL_DEV_BUS is not set
# CONFIG_VIRTIO_CONSOLE is not set
CONFIG_HW_RANDOM=y
CONFIG_UML_RANDOM=y
CONFIG_DEVMEM=y
# CONFIG_RAW_DRIVER is not set
# end of Character devices

# CONFIG_RANDOM_TRUST_BOOTLOADER is not set

#
# I2C support
#
# CONFIG_I2C is not set
# end of I2C support

# CONFIG_I3C is not set
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
# CONFIG_PPS is not set

#
# PTP clock support
#
# CONFIG_PTP_1588_CLOCK is not set

#
# Enable PHYLIB and NETWORK_PHY_TIMESTAMPING to see the additional clocks.
#
# end of PTP clock support

# CONFIG_PINCTRL is not set
# CONFIG_GPIOLIB is not set
# CONFIG_POWER_RESET is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_THERMAL is not set
# CONFIG_WATCHDOG is not set
# CONFIG_REGULATOR is not set
# CONFIG_MEDIA_CEC_SUPPORT is not set

#
# Graphics support
#
# end of Graphics support

CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_RTC_CLASS is not set

#
# DMABUF options
#
# CONFIG_SYNC_FILE is not set
# CONFIG_DMABUF_MOVE_NOTIFY is not set
# CONFIG_DMABUF_DEBUG is not set
# CONFIG_DMABUF_HEAPS is not set
# end of DMABUF options

# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set
# CONFIG_VFIO is not set
# CONFIG_VIRT_DRIVERS is not set
CONFIG_VIRTIO_MENU=y
# CONFIG_VDPA is not set
CONFIG_VHOST_MENU=y
# CONFIG_VHOST_NET is not set
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set

#
# Microsoft Hyper-V guest support
#
# end of Microsoft Hyper-V guest support

# CONFIG_GREYBUS is not set
# CONFIG_COMEDI is not set
# CONFIG_STAGING is not set
# CONFIG_COMMON_CLK is not set
# CONFIG_HWSPINLOCK is not set

#
# Clock Source drivers
#
# end of Clock Source drivers

# CONFIG_MAILBOX is not set
CONFIG_IOMMU_SUPPORT=y

#
# Generic IOMMU Pagetable Support
#
# end of Generic IOMMU Pagetable Support

#
# Remoteproc drivers
#
# end of Remoteproc drivers

#
# Rpmsg drivers
#
# end of Rpmsg drivers

#
# SOC (System On Chip) specific Drivers
#

#
# Amlogic SoC drivers
#
# end of Amlogic SoC drivers

#
# Broadcom SoC drivers
#
# end of Broadcom SoC drivers

#
# NXP/Freescale QorIQ SoC drivers
#
# end of NXP/Freescale QorIQ SoC drivers

#
# i.MX SoC drivers
#
# end of i.MX SoC drivers

#
# Enable LiteX SoC Builder specific drivers
#
# end of Enable LiteX SoC Builder specific drivers

#
# Qualcomm SoC drivers
#
# end of Qualcomm SoC drivers

# CONFIG_SOC_TI is not set

#
# Xilinx SoC drivers
#
# end of Xilinx SoC drivers
# end of SOC (System On Chip) specific Drivers

# CONFIG_PM_DEVFREQ is not set
# CONFIG_EXTCON is not set
# CONFIG_MEMORY is not set
# CONFIG_IIO is not set
# CONFIG_PWM is not set

#
# IRQ chip support
#
# end of IRQ chip support

# CONFIG_RESET_CONTROLLER is not set

#
# PHY Subsystem
#
# CONFIG_GENERIC_PHY is not set
# end of PHY Subsystem

# CONFIG_POWERCAP is not set
# CONFIG_RAS is not set

#
# Android
#
# CONFIG_ANDROID is not set
# end of Android

# CONFIG_DAX is not set
# CONFIG_NVMEM is not set

#
# HW tracing support
#
# CONFIG_STM is not set
# end of HW tracing support

# CONFIG_FPGA is not set
# CONFIG_TEE is not set
# CONFIG_SIOX is not set
# CONFIG_SLIMBUS is not set
# CONFIG_INTERCONNECT is not set
# CONFIG_COUNTER is not set
# end of Device Drivers

#
# File systems
#
# CONFIG_VALIDATE_FS_PARSER is not set
CONFIG_FS_IOMAP=y
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT2=y
# CONFIG_EXT4_FS_POSIX_ACL is not set
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_REISERFS_FS_XATTR is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
# CONFIG_F2FS_FS is not set
# CONFIG_FS_DAX is not set
CONFIG_EXPORTFS=y
# CONFIG_EXPORTFS_BLOCK_OPS is not set
CONFIG_FILE_LOCKING=y
CONFIG_MANDATORY_FILE_LOCKING=y
# CONFIG_FS_ENCRYPTION is not set
# CONFIG_FS_VERITY is not set
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_FANOTIFY is not set
CONFIG_QUOTA=y
# CONFIG_QUOTA_NETLINK_INTERFACE is not set
CONFIG_PRINT_QUOTA_WARNING=y
# CONFIG_QUOTA_DEBUG is not set
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
CONFIG_QUOTACTL=y
CONFIG_AUTOFS4_FS=m
CONFIG_AUTOFS_FS=m
# CONFIG_FUSE_FS is not set
# CONFIG_OVERLAY_FS is not set

#
# Caches
#
# CONFIG_FSCACHE is not set
# end of Caches

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set
# end of CD-ROM/DVD Filesystems

#
# DOS/FAT/EXFAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_EXFAT_FS is not set
# CONFIG_NTFS_FS is not set
# end of DOS/FAT/EXFAT/NT Filesystems

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
# CONFIG_PROC_CHILDREN is not set
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_TMPFS_XATTR is not set
# CONFIG_TMPFS_INODE64 is not set
CONFIG_MEMFD_CREATE=y
# CONFIG_CONFIGFS_FS is not set
# end of Pseudo filesystems

CONFIG_MISC_FILESYSTEMS=y
# CONFIG_ORANGEFS_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_SQUASHFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_OMFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX6FS_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_PSTORE is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_EROFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_CEPH_FS is not set
# CONFIG_CIFS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_MAC_ROMAN is not set
# CONFIG_NLS_MAC_CELTIC is not set
# CONFIG_NLS_MAC_CENTEURO is not set
# CONFIG_NLS_MAC_CROATIAN is not set
# CONFIG_NLS_MAC_CYRILLIC is not set
# CONFIG_NLS_MAC_GAELIC is not set
# CONFIG_NLS_MAC_GREEK is not set
# CONFIG_NLS_MAC_ICELAND is not set
# CONFIG_NLS_MAC_INUIT is not set
# CONFIG_NLS_MAC_ROMANIAN is not set
# CONFIG_NLS_MAC_TURKISH is not set
# CONFIG_NLS_UTF8 is not set
# CONFIG_UNICODE is not set
CONFIG_IO_WQ=y
# end of File systems

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y
# CONFIG_HARDENED_USERCOPY is not set
# CONFIG_STATIC_USERMODEHELPER is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_LSM="landlock,lockdown,yama,loadpin,safesetid,integrity,bpf"

#
# Kernel hardening options
#

#
# Memory initialization
#
CONFIG_INIT_STACK_NONE=y
# CONFIG_INIT_ON_ALLOC_DEFAULT_ON is not set
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
# end of Memory initialization
# end of Kernel hardening options
# end of Security options

CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
# CONFIG_CRYPTO_MANAGER is not set
# CONFIG_CRYPTO_USER is not set
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
# CONFIG_CRYPTO_AUTHENC is not set
# CONFIG_CRYPTO_TEST is not set

#
# Public-key cryptography
#
# CONFIG_CRYPTO_RSA is not set
# CONFIG_CRYPTO_DH is not set
# CONFIG_CRYPTO_ECDH is not set
# CONFIG_CRYPTO_ECDSA is not set
# CONFIG_CRYPTO_ECRDSA is not set
# CONFIG_CRYPTO_SM2 is not set
# CONFIG_CRYPTO_CURVE25519 is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_CHACHA20POLY1305 is not set
# CONFIG_CRYPTO_AEGIS128 is not set
# CONFIG_CRYPTO_SEQIV is not set
# CONFIG_CRYPTO_ECHAINIV is not set

#
# Block modes
#
# CONFIG_CRYPTO_CBC is not set
# CONFIG_CRYPTO_CFB is not set
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
# CONFIG_CRYPTO_ECB is not set
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_OFB is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set
# CONFIG_CRYPTO_KEYWRAP is not set
# CONFIG_CRYPTO_ADIANTUM is not set
# CONFIG_CRYPTO_ESSIV is not set

#
# Hash modes
#
# CONFIG_CRYPTO_CMAC is not set
# CONFIG_CRYPTO_HMAC is not set
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
# CONFIG_CRYPTO_CRC32 is not set
# CONFIG_CRYPTO_XXHASH is not set
# CONFIG_CRYPTO_BLAKE2B is not set
# CONFIG_CRYPTO_BLAKE2S is not set
# CONFIG_CRYPTO_CRCT10DIF is not set
# CONFIG_CRYPTO_GHASH is not set
# CONFIG_CRYPTO_POLY1305 is not set
# CONFIG_CRYPTO_MD4 is not set
# CONFIG_CRYPTO_MD5 is not set
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_SHA3 is not set
# CONFIG_CRYPTO_SM3 is not set
# CONFIG_CRYPTO_STREEBOG is not set
# CONFIG_CRYPTO_WP512 is not set

#
# Ciphers
#
# CONFIG_CRYPTO_AES is not set
# CONFIG_CRYPTO_AES_TI is not set
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
# CONFIG_CRYPTO_DES is not set
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_CHACHA20 is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_SM4 is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set

#
# Compression
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not set
# CONFIG_CRYPTO_842 is not set
# CONFIG_CRYPTO_LZ4 is not set
# CONFIG_CRYPTO_LZ4HC is not set
# CONFIG_CRYPTO_ZSTD is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
# CONFIG_CRYPTO_DRBG_MENU is not set
# CONFIG_CRYPTO_JITTERENTROPY is not set
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
# CONFIG_CRYPTO_USER_API_RNG is not set
# CONFIG_CRYPTO_USER_API_AEAD is not set

#
# Crypto library routines
#
# CONFIG_CRYPTO_LIB_BLAKE2S is not set
# CONFIG_CRYPTO_LIB_CHACHA is not set
# CONFIG_CRYPTO_LIB_CURVE25519 is not set
CONFIG_CRYPTO_LIB_POLY1305_RSIZE=11
# CONFIG_CRYPTO_LIB_POLY1305 is not set
# CONFIG_CRYPTO_LIB_CHACHA20POLY1305 is not set
CONFIG_CRYPTO_HW=y

#
# Certificates for signature checking
#
# end of Certificates for signature checking

#
# Library routines
#
# CONFIG_PACKING is not set
CONFIG_BITREVERSE=y
CONFIG_GENERIC_NET_UTILS=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
# CONFIG_CORDIC is not set
# CONFIG_PRIME_NUMBERS is not set
# CONFIG_CRC_CCITT is not set
CONFIG_CRC16=y
# CONFIG_CRC_T10DIF is not set
# CONFIG_CRC_ITU_T is not set
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
# CONFIG_CRC64 is not set
# CONFIG_CRC4 is not set
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
# CONFIG_CRC8 is not set
# CONFIG_RANDOM32_SELFTEST is not set
# CONFIG_XZ_DEC is not set
CONFIG_NO_DMA=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
# CONFIG_DMA_API_DEBUG is not set
CONFIG_DQL=y
CONFIG_NLATTR=y
# CONFIG_IRQ_POLL is not set
CONFIG_SBITMAP=y
# CONFIG_STRING_SELFTEST is not set
# end of Library routines

#
# Kernel hacking
#

#
# printk and dmesg options
#
# CONFIG_PRINTK_TIME is not set
# CONFIG_PRINTK_CALLER is not set
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DYNAMIC_DEBUG_CORE is not set
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
# end of printk and dmesg options

#
# Compile-time checks and compiler options
#
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set
# CONFIG_DEBUG_INFO_SPLIT is not set
CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT=y
# CONFIG_DEBUG_INFO_DWARF4 is not set
# CONFIG_DEBUG_INFO_DWARF5 is not set
# CONFIG_DEBUG_INFO_BTF is not set
# CONFIG_GDB_SCRIPTS is not set
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
CONFIG_FRAME_POINTER=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# end of Compile-time checks and compiler options

#
# Generic Kernel Debugging Instruments
#
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_MAGIC_SYSRQ_SERIAL=y
CONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE=""
# CONFIG_DEBUG_FS is not set
# CONFIG_UBSAN is not set
# end of Generic Kernel Debugging Instruments

CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_MISC=y

#
# Memory Debugging
#
# CONFIG_PAGE_EXTENSION is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_SCHED_STACK_END_CHECK is not set
# CONFIG_DEBUG_VM is not set
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_CC_HAS_KASAN_GENERIC=y
# end of Memory Debugging

# CONFIG_DEBUG_SHIRQ is not set

#
# Debug Oops, Lockups and Hangs
#
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
# CONFIG_SOFTLOCKUP_DETECTOR is not set
# CONFIG_DETECT_HUNG_TASK is not set
# CONFIG_WQ_WATCHDOG is not set
# CONFIG_TEST_LOCKUP is not set
# end of Debug Oops, Lockups and Hangs

#
# Scheduler Debugging
#
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# end of Scheduler Debugging

# CONFIG_DEBUG_TIMEKEEPING is not set

#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_WW_MUTEX_SELFTEST is not set
# CONFIG_SCF_TORTURE_TEST is not set
# CONFIG_CSD_LOCK_WAIT_DEBUG is not set
# end of Lock Debugging (spinlocks, mutexes, etc...)

# CONFIG_DEBUG_IRQFLAGS is not set
CONFIG_STACKTRACE=y
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_HAVE_DEBUG_BUGVERBOSE=y

#
# Debug kernel data structures
#
# CONFIG_DEBUG_LIST is not set
# CONFIG_DEBUG_PLIST is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_BUG_ON_DATA_CORRUPTION is not set
# end of Debug kernel data structures

# CONFIG_DEBUG_CREDENTIALS is not set

#
# RCU Debugging
#
# CONFIG_RCU_SCALE_TEST is not set
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_RCU_REF_SCALE_TEST is not set
# CONFIG_RCU_TRACE is not set
# CONFIG_RCU_EQS_DEBUG is not set
# end of RCU Debugging

# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_LATENCYTOP is not set
CONFIG_TRACING_SUPPORT=y
CONFIG_FTRACE=y
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_HWLAT_TRACER is not set
# CONFIG_ENABLE_DEFAULT_TRACERS is not set
# CONFIG_TRACER_SNAPSHOT is not set
CONFIG_BRANCH_PROFILE_NONE=y
# CONFIG_PROFILE_ANNOTATED_BRANCHES is not set
# CONFIG_PROFILE_ALL_BRANCHES is not set
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_SYNTH_EVENTS is not set
# CONFIG_TRACEPOINT_BENCHMARK is not set
# CONFIG_PREEMPTIRQ_DELAY_TEST is not set
# CONFIG_SAMPLES is not set

#
# um Debugging
#
# CONFIG_GPROF is not set
CONFIG_EARLY_PRINTK=y
# end of um Debugging

#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_ARCH_HAS_KCOV=y
CONFIG_RUNTIME_TESTING_MENU=y
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_TEST_MIN_HEAP is not set
# CONFIG_TEST_SORT is not set
# CONFIG_TEST_DIV64 is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
# CONFIG_REED_SOLOMON_TEST is not set
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_TEST_HEXDUMP is not set
# CONFIG_TEST_STRING_HELPERS is not set
# CONFIG_TEST_STRSCPY is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_TEST_PRINTF is not set
# CONFIG_TEST_SCANF is not set
# CONFIG_TEST_BITMAP is not set
# CONFIG_TEST_UUID is not set
# CONFIG_TEST_XARRAY is not set
# CONFIG_TEST_OVERFLOW is not set
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_TEST_HASH is not set
# CONFIG_TEST_IDA is not set
# CONFIG_TEST_LKM is not set
# CONFIG_TEST_BITOPS is not set
# CONFIG_TEST_VMALLOC is not set
# CONFIG_TEST_USER_COPY is not set
# CONFIG_TEST_BPF is not set
# CONFIG_TEST_BLACKHOLE_DEV is not set
# CONFIG_FIND_BIT_BENCHMARK is not set
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_SYSCTL is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_TEST_STATIC_KEYS is not set
# CONFIG_TEST_KMOD is not set
# CONFIG_TEST_MEMCAT_P is not set
# CONFIG_TEST_STACKINIT is not set
# CONFIG_TEST_MEMINIT is not set
# CONFIG_TEST_FREE_PAGES is not set
# end of Kernel Testing and Coverage
# end of Kernel hacking

[-- Attachment #3: Type: text/plain, Size: 152 bytes --]

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

> If possible, please share your userspace. Maybe the ld.so you're using 
> is
> special and triggers the bug.
> 
> Thanks,
> //richard

I have attached it now.

The rootfs which contains this ls.so is from the Google net_test 
framework.
https://android.googlesource.com/kernel/tests/+/refs/heads/master/net/test/run_net_test.sh#86

You can download it using -

wget -nv https://dl.google.com/dl/android/net_test.rootfs.20150203.xz
unxz net_test.rootfs.20150203.xz

[-- Attachment #2: ld-2.13.so --]
[-- Type: application/x-sharedlib, Size: 136936 bytes --]

[-- Attachment #3: Type: text/plain, Size: 152 bytes --]

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Johannes Berg]

On Tue, 2021-07-13 at 12:02 -0600, subashab@codeaurora.org wrote:
> > If possible, please share your userspace. Maybe the ld.so you're
> > using 
> > is
> > special and triggers the bug.
> > 
> > Thanks,
> > //richard
> 
> I have attached it now.
> 
> The rootfs which contains this ls.so is from the Google net_test 
> framework.

Well, I think Richard meant your *hosts* ld.so, not your rootfs inside
the guest/VM.

FWIW, even with your config I cannot reproduce this.

johannes


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

[-- Attachment #1: Type: text/plain, Size: 203 bytes --]

> Well, I think Richard meant your *hosts* ld.so, not your rootfs inside
> the guest/VM.
> 
> FWIW, even with your config I cannot reproduce this.
> 
> johannes

Sure, I have attached the host ld.so now.

[-- Attachment #2: ld-2.23.so --]
[-- Type: application/x-sharedlib, Size: 162632 bytes --]

[-- Attachment #3: Type: text/plain, Size: 152 bytes --]

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Johannes Berg]

On Tue, 2021-07-13 at 12:54 -0600, subashab@codeaurora.org wrote:
> > Well, I think Richard meant your *hosts* ld.so, not your rootfs
> > inside
> > the guest/VM.
> > 
> > FWIW, even with your config I cannot reproduce this.
> > 
> > johannes
> 
> Sure, I have attached the host ld.so now.

Wasn't compatible with my system ... can you describe the host system?

johannes


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Johannes Berg]

On Sat, 2021-07-10 at 15:00 -0600, subashab@codeaurora.org wrote:
> 
> I have reverted the following patches (to allow for a clean revert)
> and I don't see the panic anymore -
> 
> bfc58e2b98e99737409cd9f4d86a79677c5b887c
> dc01a3b9db43abf95b801c9694980777a329e303
> 9f0b4807a44ff81cf59421c8a86641efec586610
> 84b2789d61156db0224724806b20110c0d34b07c

Out of those 4, the last ("separate child and...") seems actually less
intrusive than the previous one. If you revert only the first three of
this list, does it still happen?

Does it still happen if you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and do
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead?

johannes


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Johannes Berg]

On Tue, 2021-07-13 at 21:22 +0200, Johannes Berg wrote:
> On Sat, 2021-07-10 at 15:00 -0600, subashab@codeaurora.org wrote:
> > 
> > I have reverted the following patches (to allow for a clean revert)
> > and I don't see the panic anymore -
> > 
> > bfc58e2b98e99737409cd9f4d86a79677c5b887c
> > dc01a3b9db43abf95b801c9694980777a329e303
> > 9f0b4807a44ff81cf59421c8a86641efec586610
> > 84b2789d61156db0224724806b20110c0d34b07c
> 
> Out of those 4, the last ("separate child and...") seems actually less
> intrusive than the previous one. If you revert only the first three of
> this list, does it still happen?
> 
> Does it still happen if you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and do
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead?

Oh, and it looks like 84b2789d6115 actually got some bits that shouldn't
have been there!

Assuming it does *not* work with just the first three patches reverted,
does it work again if you revert the first three patches, and only this
bit of the fourth?

--- a/arch/um/kernel/skas/clone.c
+++ b/arch/um/kernel/skas/clone.c
@@ -24,29 +24,26 @@
 void __attribute__ ((__section__ (".__syscall_stub")))
 stub_clone_handler(void)
 {
-       struct stub_data *data = (struct stub_data *) STUB_DATA;
+       int stack;
+       struct stub_data *data = (void *) ((unsigned long)&stack & ~(UM_KERN_PAGE_SIZE - 1));
        long err;



I think we probably have some miscompilation again with this thing - I
saw a bunch of similar issues with our syscall stubs at some point, and
I'm not sure we got it all right already.

johannes


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Johannes Berg]

On Tue, 2021-07-13 at 21:26 +0200, Johannes Berg wrote:
> On Tue, 2021-07-13 at 21:22 +0200, Johannes Berg wrote:
> > On Sat, 2021-07-10 at 15:00 -0600, subashab@codeaurora.org wrote:
> > > 
> > > I have reverted the following patches (to allow for a clean revert)
> > > and I don't see the panic anymore -
> > > 
> > > bfc58e2b98e99737409cd9f4d86a79677c5b887c
> > > dc01a3b9db43abf95b801c9694980777a329e303
> > > 9f0b4807a44ff81cf59421c8a86641efec586610
> > > 84b2789d61156db0224724806b20110c0d34b07c
> > 
> > Out of those 4, the last ("separate child and...") seems actually less
> > intrusive than the previous one. If you revert only the first three of
> > this list, does it still happen?
> > 
> > Does it still happen if you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and do
> > CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead?
> 
> Oh, and it looks like 84b2789d6115 actually got some bits that shouldn't
> have been there!
> 
> Assuming it does *not* work with just the first three patches reverted,
> does it work again if you revert the first three patches, and only this
> bit of the fourth?

[snip]

And as yet another experiment in this area, does it work again if you
apply this patch?

https://patchwork.ozlabs.org/project/linux-um/patch/20210303155523.124277-11-benjamin@sipsolutions.net/

Not sure it applies as-is, but you can see the schema there.

johannes


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

> Wasn't compatible with my system ... can you describe the host system?
> 
> johannes

Its an Intel 8th gen i7 with Ubuntu 16.04 LTS.
Kernel version is 4.15.0-70-generic.
gcc version is 5.4.

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

On 2021-07-13 13:22, Johannes Berg wrote:
> On Sat, 2021-07-10 at 15:00 -0600, subashab@codeaurora.org wrote:
>> 
>> I have reverted the following patches (to allow for a clean revert)
>> and I don't see the panic anymore -
>> 
>> bfc58e2b98e99737409cd9f4d86a79677c5b887c
>> dc01a3b9db43abf95b801c9694980777a329e303
>> 9f0b4807a44ff81cf59421c8a86641efec586610
>> 84b2789d61156db0224724806b20110c0d34b07c
> 
> Out of those 4, the last ("separate child and...") seems actually less
> intrusive than the previous one. If you revert only the first three of
> this list, does it still happen?
> 

If only the first three reverts are applied, UML seems to hang during 
initialization-

printk: console [mc-1] enabled
EXT4-fs (ubda): mounting ext3 file system using the ext4 subsystem
EXT4-fs (ubda): mounted filesystem with ordered data mode. Opts: (null). 
Quota mode: none.
VFS: Mounted root (ext3 filesystem) readonly on device 98:0.
devtmpfs: mounted
This architecture does not have kernel memory protection.
Run /sbin/init as init process
INIT: version 2.88 booting
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
random: fast init done
random: crng init done
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..
copy_context_skas0 - stub-parent reports error 3
INIT: cannot fork, retry..


> Does it still happen if you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and do
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead?
> 
> johannes

If none of the reverts are applied and I set 
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE,
I still see the initialization crash.

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

> Oh, and it looks like 84b2789d6115 actually got some bits that 
> shouldn't
> have been there!
> 
> Assuming it does *not* work with just the first three patches reverted,
> does it work again if you revert the first three patches, and only this
> bit of the fourth?
> 
> --- a/arch/um/kernel/skas/clone.c
> +++ b/arch/um/kernel/skas/clone.c
> @@ -24,29 +24,26 @@
>  void __attribute__ ((__section__ (".__syscall_stub")))
>  stub_clone_handler(void)
>  {
> -       struct stub_data *data = (struct stub_data *) STUB_DATA;
> +       int stack;
> +       struct stub_data *data = (void *) ((unsigned long)&stack &
> ~(UM_KERN_PAGE_SIZE - 1));
>         long err;
> 
> 
> 
> I think we probably have some miscompilation again with this thing - I
> saw a bunch of similar issues with our syscall stubs at some point, and
> I'm not sure we got it all right already.
> 
> johannes

Initialization is successful if only this bit of 
84b2789d61156db0224724806b20110c0d34b07c
is reverted.


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[subashab]

> [snip]
> 
> And as yet another experiment in this area, does it work again if you
> apply this patch?
> 
> https://patchwork.ozlabs.org/project/linux-um/patch/20210303155523.124277-11-benjamin@sipsolutions.net/
> 
> Not sure it applies as-is, but you can see the schema there.
> 
> johannes

If this patch is applied without any reverts the crash is seen.
If patch is applied with the 3 reverts applied, the initialization
is hanging.

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Johannes Berg]

On Tue, 2021-07-13 at 14:40 -0600, subashab@codeaurora.org wrote:
> > [snip]
> > 
> > And as yet another experiment in this area, does it work again if
> > you
> > apply this patch?
> > 
> > https://patchwork.ozlabs.org/project/linux-um/patch/20210303155523.124277-11-benjamin@sipsolutions.net/
> > 
> > Not sure it applies as-is, but you can see the schema there.
> > 
> > johannes
> 
> If this patch is applied without any reverts the crash is seen.
> If patch is applied with the 3 reverts applied, the initialization
> is hanging.
> 
IOW, it didn't change anything :)

Thanks for all the experiments, we're looking at the compilation
especially wrt. that one reverted hunk now.

johannes


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[YiFei Zhu]

On Tue, Jul 13, 2021 at 3:00 PM <subashab@codeaurora.org> wrote:
>
> > Wasn't compatible with my system ... can you describe the host system?
> >
> > johannes
>
> Its an Intel 8th gen i7 with Ubuntu 16.04 LTS.
> Kernel version is 4.15.0-70-generic.
> gcc version is 5.4.

FWIW, for me, compiling UML with defconfig inside a Ubuntu 16.04
docker is enough to produce a binary that could trigger a crash even
outside docker, using hostfs root mount (so no special ld.so).

This is some sort of compiler difference.

YiFei Zhu

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um

Re: UML kernel panic on initialization

[Richard Weinberger]

----- Ursprüngliche Mail -----
> Von: "YiFei Zhu" <zhuyifei1999@gmail.com>
> An: "subashab" <subashab@codeaurora.org>
> CC: "Johannes Berg" <johannes@sipsolutions.net>, "richard" <richard@nod.at>, "anton ivanov"
> <anton.ivanov@cambridgegreys.com>, "Jeff Dike" <jdike@addtoit.com>, "linux-um" <linux-um@lists.infradead.org>,
> "stranche" <stranche@codeaurora.org>
> Gesendet: Dienstag, 13. Juli 2021 22:52:43
> Betreff: Re: UML kernel panic on initialization

> On Tue, Jul 13, 2021 at 3:00 PM <subashab@codeaurora.org> wrote:
>>
>> > Wasn't compatible with my system ... can you describe the host system?
>> >
>> > johannes
>>
>> Its an Intel 8th gen i7 with Ubuntu 16.04 LTS.
>> Kernel version is 4.15.0-70-generic.
>> gcc version is 5.4.
> 
> FWIW, for me, compiling UML with defconfig inside a Ubuntu 16.04
> docker is enough to produce a binary that could trigger a crash even
> outside docker, using hostfs root mount (so no special ld.so).
> 
> This is some sort of compiler difference.

Exactly. :-)
Please see Johannes' patch:
http://lists.infradead.org/pipermail/linux-um/2021-July/001571.html

Thanks,
//richard

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um