Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1180293
| From | Jason Gunthorpe <jgunthorpe@obsidianresearch.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v4 3/5] tee: generic TEE subsystem |
| Date | 2015-07-09 01:20 +0200 |
| Message-ID | <pK6Nc-Ym-9@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <pJUCl-1ra-19@gated-at.bofh.it> <pK1aO-5wA-3@gated-at.bofh.it> <pK4V4-88w-11@gated-at.bofh.it> <pK60O-oY-23@gated-at.bofh.it> <pK6au-ti-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Jul 08, 2015 at 03:33:25PM -0700, Greg Kroah-Hartman wrote:
> > The basic issue is that cdev_del doesn't seem to be synchronizing.
> >
> > The use after free race is then something like:
> >
> > struct tpm_chip {
> > struct device dev;
> > struct cdev cdev;
>
> Oops, right there's your problem. You can't have two reference counted
> objects trying to manage the memory of a single structure. No matter
> what you do, it's going to be a pain to deal with this, so don't :)
Sure, generally, yes, but that isn't done for no reason, it is to make
open straightforward:
static int tpm_open(struct inode *inode, struct file *file)
{
struct tpm_chip *chip =
container_of(inode->i_cdev, struct tpm_chip, cdev);
We need to recover the tpm_chip associated with the char device
node, in a way that is holding a kref on it, without racing with
cdev_del/etc
This scheme does mean that if we have a struct file we have a kref on
the cdev, and if we have cdev then we have a kref on the tpm_chip,
which is really easy to use properly.
> > Ie we need cdev to hold a ref on tpm_chip->dev until cdev_put is
> > called.
>
> No, separate them, make the cdev a pointer and all should be fine.
Okay, cdev_alloc takes care of the cdev lifetime.
Do you have a simple solution to replace container_of as well?
What would you think about something like:
cdev_alloc(&chip->dev.kref)
?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH v4 3/5] tee: generic TEE subsystem Jason Gunthorpe <jgunthorpe@obsidianresearch.com> - 2015-07-09 01:20 +0200
Re: [PATCH v4 3/5] tee: generic TEE subsystem Greg Kroah-Hartman <gregkh@linuxfoundation.org> - 2015-07-09 02:00 +0200
Re: [PATCH v4 3/5] tee: generic TEE subsystem Dmitry Torokhov <dmitry.torokhov@gmail.com> - 2015-07-09 02:50 +0200
csiph-web