[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131115041324.GA28088@kroah.com>
Date: Fri, 15 Nov 2013 13:13:24 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Peng Tao <bergwolf@...il.com>
Cc: linux-kernel@...r.kernel.org,
"John L. Hammond" <john.hammond@...el.com>,
Andreas Dilger <andreas.dilger@...el.com>
Subject: Re: [PATCH 05/40] staging/lustre: validate open handle cookies
On Fri, Nov 15, 2013 at 12:13:07AM +0800, Peng Tao wrote:
> From: "John L. Hammond" <john.hammond@...el.com>
>
> Add a const void *h_owner member to struct portals_handle. Add a const
> void *owner parameter to class_handle2object() which must be matched
> by the h_owner member of the handle in addition to the cookie.
Ick ick ick.
NEVER use a void pointer if you can help it, and for a "handle", never.
This isn't other operating systems, sorry. We know what types our
pointers to structures are, use them, so that the compiler can catch our
problems, and don't try to cheat by using void *.
> Adjust
> the callers of class_handle2object() accordingly, using NULL as the
> argument to the owner parameter, except in the case of
> mdt_handle2mfd() where we add an explicit mdt_export_data parameter
> which we use as the owner when searching for a MFD. When allocating a
> new MFD, pass a pointer to the mdt_export_data into mdt_mfd_new() and
> store it in h_owner. This allows the MDT to validate that the client
> has not sent the wrong open handle cookie, or sent the right cookie to
> the wrong MDT.
This changelog entry doesn't even match up with the code below. ALl
callers of class_handle2object are passing NULL here, which makes this
patch pretty pointless, right?
And that's a _very_ generic global symbol name, please don't do that, it
needs to be "lustre_*" at the front to even expect it to be acceptable.
thanks,
greg k-h
--
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/
Powered by blists - more mailing lists