Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1677097
| From | Bjorn Andersson <bjorn.andersson@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops |
| Date | 2017-06-28 21:30 +0200 |
| Message-ID | <tXqP0-1wb-15@gated-at.bofh.it> (permalink) |
| References | <tNT5T-rX-15@gated-at.bofh.it> <tWnJw-1Zo-17@gated-at.bofh.it> <tWybV-qo-45@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon 26 Jun 02:04 PDT 2017, Henri Roosen wrote: > On 06/25/2017 11:51 PM, Bjorn Andersson wrote: > > On Fri 02 Jun 04:35 PDT 2017, Henri Roosen wrote: > > > > > A device might not have an ops structure registered. This > > > patch fixes a null-prt dereference by checking ops before dereferencing > > > it. > > > > > > > In what scenario do you end up with a rpdev without ops defined? > > > > You need at least create_ept defined in your ops to be able to do any > > form of communication. So it would probably make more sense to add a > > sanity check in rpmsg_register_device(), but perhaps I'm missing > > something. > > I was trying to add support for the generic rpmsg-char driver for > virtio_rpmsg_bus. > > The rpmsg-char driver gets registered using rpmsg_chrdev_register_device(), > and IMHO this device should not have any > .ops. The chrdev is not used for communication, only for creating devices. > The devices which should have the .ops are the ones created using the > rpmsg-char device. > In order to create/open new channels from user space you need to call rpmsg_create_ept() and this require a rpmsg_device context in order for the communication to be associated with the appropriate link. So we must set up the rpmsg_device context with the ops table including create_ept() in order to maintain the reference back to the particular virtio device (or SMD channel). The main difference from previous implementations of this is that the rpmsg_device does not have a primary endpoint. This removes the need for the firmware to create a special channel to instantiate the user space communication, but comes at the cost of the special spawning from the individual backend drivers. Regards, Bjorn
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops Bjorn Andersson <bjorn.andersson@linaro.org> - 2017-06-26 00:00 +0200
Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops Henri Roosen <henri.roosen@ginzinger.com> - 2017-06-26 11:10 +0200
Re: [PATCH] rpmsg: rpmsg_core: fix null-ptr dereference for devices without ops Bjorn Andersson <bjorn.andersson@linaro.org> - 2017-06-28 21:30 +0200
csiph-web