lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <253lee4shg0.fsf@mtr-vdi-124.i-did-not-set--mail-host-address--so-tickle-me> Date: Mon, 21 Aug 2023 15:33:51 +0300 From: Aurelien Aptel <aaptel@...dia.com> To: Sagi Grimberg <sagi@...mberg.me>, linux-nvme@...ts.infradead.org, netdev@...r.kernel.org, hch@....de, kbusch@...nel.org, axboe@...com, chaitanyak@...dia.com, davem@...emloft.net, kuba@...nel.org Cc: Or Gerlitz <ogerlitz@...dia.com>, aurelien.aptel@...il.com, smalin@...dia.com, malin1024@...il.com, yorayz@...dia.com, borisp@...dia.com, galshalom@...dia.com, mgurtovoy@...dia.com Subject: Re: [PATCH v12 10/26] nvme-tcp: Deal with netdevice DOWN events Sagi Grimberg <sagi@...mberg.me> writes: > I'm assuming you are running with lockdep and friends? We tested it under the following configuration: CONFIG_LOCKDEP_SUPPORT=y CONFIG_PROVE_LOCKING=y CONFIG_PROVE_RAW_LOCK_NESTING=y CONFIG_LOCKDEP=y CONFIG_LOCKDEP_BITS=15 CONFIG_LOCKDEP_CHAINS_BITS=16 CONFIG_LOCKDEP_STACK_TRACE_BITS=19 CONFIG_LOCKDEP_STACK_TRACE_HASH_BITS=14 CONFIG_LOCKDEP_CIRCULAR_QUEUE_BITS=12 CONFIG_DEBUG_LOCKDEP=y CONFIG_PROVE_RCU=y No warnings were printed in dmesg. Anything else we should verify?
Powered by blists - more mailing lists