From: Greg KH <greg@kroah.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [PATCH] usb_string fix
Date: Mon, 5 Aug 2002 15:36:20 -0700 [thread overview]
Message-ID: <20020805223620.GC29396@kroah.com> (raw)
In-Reply-To: <UTC200208052142.g75Lg9C25845.aeb@smtp.cwi.nl>
On Mon, Aug 05, 2002 at 11:42:09PM +0200, Andries.Brouwer@cwi.nl wrote:
>
> [I thought I sent this yesterday night, but don't see it on l-k,
> maybe I forgot. Sorry if I send it twice.]
>
> Things are indeed as conjectured, and I can reproduce the situation
> where usb_string() returns -EPIPE. Now that this is an internal
> error code for the USB subsystem, and not meant to get out to the
> user, I made these driverfs files empty in case of error.
> (While if there is no error but the string has length 0,
> the file will consist of a single '\n'.)
>
> One fewer random memory corruption. Unfortunately, there are more.
Thanks for the fix, I've applied it to my trees.
greg k-h
prev parent reply other threads:[~2002-08-05 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 21:42 [PATCH] usb_string fix Andries.Brouwer
2002-08-05 22:36 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020805223620.GC29396@kroah.com \
--to=greg@kroah.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox