Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1327698 > unrolled thread
| Started by | Jiri Kosina <jikos@kernel.org> |
|---|---|
| First post | 2016-02-05 14:40 +0100 |
| Last post | 2016-02-05 14:40 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] HID: Check whether if the hidraw is NULL pointer before release. Jiri Kosina <jikos@kernel.org> - 2016-02-05 14:40 +0100
| From | Jiri Kosina <jikos@kernel.org> |
|---|---|
| Date | 2016-02-05 14:40 +0100 |
| Subject | Re: [PATCH] HID: Check whether if the hidraw is NULL pointer before release. |
| Message-ID | <qYOMc-P6-51@gated-at.bofh.it> |
On Tue, 2 Feb 2016, shenpengru@gmail.com wrote: > From: shenpengru <shenpengru@xiaomi.com> > > The logic of service which operate hidraw device in user-space may > not correct, sometimes it may release hidraw dev for more than once. > In order to prevent this situation, we need to make the driver more > robust. Hmm .. how would you call close(fd) twice on the same descriptor and let it pass fput()? I'd like to better understand how we ended up in this situation. Could you please provide more details? Thanks a lot, -- Jiri Kosina SUSE Labs
Back to top | Article view | linux.kernel
csiph-web