From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF590C11D04 for ; Thu, 20 Feb 2020 10:27:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9C3F420801 for ; Thu, 20 Feb 2020 10:27:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726882AbgBTK1t (ORCPT ); Thu, 20 Feb 2020 05:27:49 -0500 Received: from mx2.suse.de ([195.135.220.15]:46154 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726801AbgBTK1t (ORCPT ); Thu, 20 Feb 2020 05:27:49 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 6A212AD39; Thu, 20 Feb 2020 10:27:47 +0000 (UTC) Message-ID: <1582194461.6843.9.camel@suse.com> Subject: Re: usb cdc-acm TIOCSSERIAL may wrongly report EPERM From: Oliver Neukum To: Anthony Mallet Cc: linux-usb@vger.kernel.org Date: Thu, 20 Feb 2020 11:27:41 +0100 In-Reply-To: <24141.6739.313167.448875@beetle.laas.fr> References: <24140.5498.228141.264272@beetle.laas.fr> <1582106185.9787.9.camel@suse.com> <24141.6739.313167.448875@beetle.laas.fr> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-usb-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-usb@vger.kernel.org Am Mittwoch, den 19.02.2020, 12:21 +0100 schrieb Anthony Mallet: > On Wednesday 19 Feb 2020, at 10:56, Oliver Neukum wrote: > > thank you for the detailed report about an unusual bug. Could you > > test the attached patch? > > I did not actually run it yet, but at first sight it seems that it will > mishandle the ASYNC_CLOSING_WAIT_NONE case. You are right. > Yes, no problem. Thank you. > I hope my patches follow the required format, I'm not sure about all > the details. The patches themselves look good. Please follow Documentation/SubmittingPatches Regards Oliver PS: my mailer seems to suffer a malfunction with HTML. Sorry for the erstwhiole empty post