linux-kernel - Re: [PATCH v2 1/1] usb: cdc-acm: handle unlinked urb in acm read callback

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151230014651.GA19447@kroah.com>
Date:	Tue, 29 Dec 2015 17:46:51 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Lu Baolu <baolu.lu@...ux.intel.com>
Cc:	Oliver Neukum <oliver@...kum.org>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Tang Jian Qiang <jianqiang.tang@...el.com>,
	stable@...r.kernel.org
Subject: Re: [PATCH v2 1/1] usb: cdc-acm: handle unlinked urb in acm read
 callback

On Wed, Dec 30, 2015 at 08:42:01AM +0800, Lu Baolu wrote:
> In current acm driver, the bulk-in callback function ignores the
> URBs unlinked in usb core.
> 
> This causes unexpected data loss in some cases. For example,
> runtime suspend entry will unlinked all urbs and set urb->status
> to -ENOENT even those urbs might have data not processed yet.
> Hence, data loss occurs.
> 
> This patch lets bulk-in callback function handle unlinked urbs
> to avoid data loss.
> 
> Signed-off-by: Tang Jian Qiang <jianqiang.tang@...el.com>
> Signed-off-by: Lu Baolu <baolu.lu@...ux.intel.com>
> Cc: stable@...r.kernel.org
> Acked-by: Oliver Neukum <oneukum@...e.com>
> ---
>  drivers/usb/class/cdc-acm.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

What changed in v2?

Please always document that below the --- line.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/