linux-kernel - Re: [PATCH 1/3] Infiniband: make ehca_pd use struct pid pointer rather than pid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <OF4F7C6111.9AA26F4F-ONC1257410.00599780-C1257410.005E3475@de.ibm.com>
Date:	Tue, 18 Mar 2008 18:09:22 +0100
From:	Hoang-Nam Nguyen <HNGUYEN@...ibm.com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Christoph Raisch <raisch@...ibm.com>,
	general@...ts.openfabrics.org,
	Hal Rosenstock <hal.rosenstock@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Roland Dreier <rolandd@...co.com>,
	Sean Hefty <sean.hefty@...el.com>,
	Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [PATCH 1/3] Infiniband: make ehca_pd use struct pid pointer rather than
 pid_t

>  > Reason for above checking is to prevent a child process releasing
>  > a resource that the parent process has created and still wants to use.
>  > Do you think that's something we can generalize into ib_core?
> Clearly if we want that check then it should be in the core uverbs
> module.  But I'm not sure why we would want that check -- I don't see
> any realistic scenario where that would cause problems, and it seems
> at least as likely that the check would break an app that
> intentionally does something clever.
Right, above checking is based on a very simple policy "creator of a
resource is also the owner in term of releasing it" and will not cover
other customized patterns. We had a case - believe on sles9, in which
a child process manipulated/released resources from parent one, and
it was not easy to find the bug.
Wrt/ your actual question: we can remove the tgid stuff from ehca kernel
code. When do you expect me to send a patch at latest?

Nam

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/