From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751995AbdCAUBz (ORCPT ); Wed, 1 Mar 2017 15:01:55 -0500 Received: from mail-it0-f54.google.com ([209.85.214.54]:36952 "EHLO mail-it0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751570AbdCAUBb (ORCPT ); Wed, 1 Mar 2017 15:01:31 -0500 MIME-Version: 1.0 In-Reply-To: References: From: Eric Dumazet Date: Wed, 1 Mar 2017 11:59:55 -0800 Message-ID: Subject: Re: net: sleeping function called from invalid context in net_enable_timestamp To: Dmitry Vyukov Cc: David Miller , netdev , LKML , Cong Wang , syzkaller Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 1, 2017 at 11:51 AM, Dmitry Vyukov wrote: > > Hello, > > I've got the following report while running syzkaller fuzzer on > e5d56efc97f8240d0b5d66c03949382b6d7e5570 Right, a listener is playing fool games. We need to use a work queue for all net_enable_timestamp() invocations