From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] usb: Use well-known descriptor sizes when parsing configuration
Date: Thu, 18 Jul 2013 20:25:54 +0200 [thread overview]
Message-ID: <201307182025.54226.marex@denx.de> (raw)
In-Reply-To: <CAODwPW9HtgutYi+CoNd54HaCrUf66jXohw3R06KhZvf6O+BhhQ@mail.gmail.com>
Dear Julius Werner,
> > From a security / robustness standpoint,
> >
> > - if the descriptor length field is found to be abnormal, then the code
> >
> > should not process the packet at all. Here it seems it only warns
> > then goes on to use the descriptor.
>
> Weren't you the guy who was so worried about poor Chinese devices who
> don't follow the spec just two mails ago?
That would have been me, not Albert. I suspect what happens below (and will
likely happen onwards, if we don't cut the crap soon) is a bullshit-fueled
discussion about nothing, so just can it. It's totally unproductive and drifting
away from the discussion about patch. ML is not the right place for duking out
this crap ...
Please, go, break a tartelette and fix your quarrel elsewhere.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-07-18 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 0:55 [U-Boot] [PATCH v2] usb: Use well-known descriptor sizes when parsing configuration Julius Werner
2013-07-18 16:43 ` Albert ARIBAUD
2013-07-18 17:11 ` Julius Werner
2013-07-18 18:25 ` Marek Vasut [this message]
2013-07-18 18:49 ` Marek Vasut
2013-07-18 19:22 ` Julius Werner
2013-07-19 1:49 ` Marek Vasut
2013-07-19 20:11 ` Julius Werner
2013-07-21 2:32 ` Marek Vasut
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=201307182025.54226.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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