From: Hyunwoo Kim <imv4bel@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: erazor_de@users.sourceforge.net, benjamin.tissoires@redhat.com,
linux-input@vger.kernel.org
Subject: Re: [PATCH] HID: roccat: Fix Use-After-Free in roccat_read
Date: Thu, 21 Jul 2022 04:01:16 -0700 [thread overview]
Message-ID: <20220721110116.GA195996@ubuntu> (raw)
In-Reply-To: <nycvar.YFH.7.76.2207211159210.19850@cbobk.fhfr.pm>
On Thu, Jul 21, 2022 at 12:00:05PM +0200, Jiri Kosina wrote:
> Don't we actually need the mutex for much longer period during
> roccat_report_event()? At minimum it's also manipulating cbuf_end.
I modified the mutex to protect most of the roccat_report_event()
in the second patch above sent in reply.
Looking again, I submitted the second patch with some confusion. Sorry.
Regards,
Hyunwoo Kim.
next prev parent reply other threads:[~2022-07-21 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 11:13 [PATCH] HID: roccat: Fix Use-After-Free in roccat_read Hyunwoo Kim
2022-06-26 12:54 ` Silvan Jegen
2022-06-26 14:59 ` Hyunwoo Kim
2022-07-21 10:00 ` Jiri Kosina
2022-07-21 11:01 ` Hyunwoo Kim [this message]
2022-09-04 17:27 ` Hyunwoo Kim
2022-09-04 19:16 ` Silvan Jegen
2022-09-04 19:33 ` Hyunwoo Kim
-- strict thread matches above, loose matches on Subject: below --
2022-06-17 18:38 Hyunwoo Kim
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=20220721110116.GA195996@ubuntu \
--to=imv4bel@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=erazor_de@users.sourceforge.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.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).