From: David Howells Subject: Re: simplify procfs code for seq_file instances V2 Date: Mon, 30 Apr 2018 16:38:18 +0100 Message-ID: <15622.1525102698@warthog.procyon.org.uk> References: <20180425154827.32251-1-hch@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: dhowells@redhat.com, Andrew Morton , Alexander Viro , linux-rtc@vger.kernel.org, Alessandro Zummo , Alexandre Belloni , devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org, Greg Kroah-Hartman , jfs-discussion@lists.sourceforge.net, linux-afs@lists.infradead.org, linux-acpi@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, Jiri Slaby , linux-ext4@vger.kernel.org, Alexey Dobriyan , megaraidlinux.pdl@broadcom.com, drbd-dev@lists.linbit.com To: Christoph Hellwig Return-path: In-Reply-To: <20180425154827.32251-1-hch@lst.de> Content-ID: <15621.1525102698.1@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Note that your kernel hits the: inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage. swapper/0/0 [HC1[1]:SC0[0]:HE0:SE1] takes: (ptrval) (fs_reclaim){?.+.}, at: fs_reclaim_acquire+0x12/0x35 {HARDIRQ-ON-W} state was registered at: fs_reclaim_acquire+0x32/0x35 kmem_cache_alloc_node_trace+0x49/0x2cf alloc_worker+0x1d/0x49 init_rescuer.part.7+0x19/0x8f workqueue_init+0xc0/0x1fe kernel_init_freeable+0xdc/0x433 kernel_init+0xa/0xf5 ret_from_fork+0x24/0x30 bug, as described here: https://groups.google.com/forum/#!msg/syzkaller-bugs/sJC3Y3hOM08/aO3z9JXoAgAJ David