From: Greg KH <greg@kroah.com>
To: Yang Xiao <92siuyang@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-usb@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab@kernel.org, Kees Cook <keescook@chromium.org>,
hans.verkuil@cisco.com, Young Xiao <YangX92@hotmail.com>
Subject: USB: s2255 & stkwebcam: fix oops with malicious USB descriptors
Date: Tue, 16 Apr 2019 12:06:56 +0200 [thread overview]
Message-ID: <20190416100656.GG896@kroah.com> (raw)
On Fri, Apr 12, 2019 at 10:14:50AM +0800, Yang Xiao wrote:
> Sorry for my mistake.
>
> I have fixed the mistake. And the attachment is the changed patch.
I can not apply attachments, please fix up and resend as documented.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Yang Xiao <92siuyang@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-usb@vger.kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab@kernel.org, Kees Cook <keescook@chromium.org>,
hans.verkuil@cisco.com, Young Xiao <YangX92@hotmail.com>
Subject: Re: [PATCH] USB: s2255 & stkwebcam: fix oops with malicious USB descriptors
Date: Tue, 16 Apr 2019 12:06:56 +0200 [thread overview]
Message-ID: <20190416100656.GG896@kroah.com> (raw)
Message-ID: <20190416100656.vDHIyYFnGuHttrDHMCrnkJVF9QKtpwd5Y-DSATyG8Lo@z> (raw)
In-Reply-To: <CAKgHYH27TtpbUKJin+WyTRUvqgpTSBRWBTp6YhsUCpVTnKfNPA@mail.gmail.com>
On Fri, Apr 12, 2019 at 10:14:50AM +0800, Yang Xiao wrote:
> Sorry for my mistake.
>
> I have fixed the mistake. And the attachment is the changed patch.
I can not apply attachments, please fix up and resend as documented.
thanks,
greg k-h
next prev reply other threads:[~2019-04-16 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 4:54 USB: s2255 & stkwebcam: fix oops with malicious USB descriptors Young Xiao
2019-04-11 4:54 ` [PATCH] " Young Xiao
2019-04-11 14:36 ` kbuild test robot
[not found] ` <CAKgHYH27TtpbUKJin+WyTRUvqgpTSBRWBTp6YhsUCpVTnKfNPA@mail.gmail.com>
2019-04-16 10:06 ` Greg KH [this message]
2019-04-16 10:06 ` Greg KH
2019-04-16 11:26 ` Johan Hovold
2019-04-16 11:26 ` [PATCH] " Johan Hovold
2019-04-16 11:33 ` Johan Hovold
2019-04-16 11:33 ` [PATCH] " Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2019-04-12 2:39 Young Xiao
2019-04-12 8:04 Bjørn Mork
2019-04-12 8:58 Young Xiao
2019-04-12 9:07 Bjørn Mork
2019-04-12 9:36 Young Xiao
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=20190416100656.GG896@kroah.com \
--to=greg@kroah.com \
--cc=92siuyang@gmail.com \
--cc=YangX92@hotmail.com \
--cc=hans.verkuil@cisco.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mchehab@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).