[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141007171703.GA30274@infradead.org>
Date: Tue, 7 Oct 2014 10:17:03 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Cc: Jeff Layton <jlayton@...marydata.com>,
linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>,
"J. Bruce Fields" <bfields@...ldses.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH v2 02/17] security: make security_file_set_fowner,
f_setown and __f_setown void return
On Tue, Oct 07, 2014 at 08:11:42PM +0300, Dmitry Kasatkin wrote:
> If file_set_fowner op is now type of "void", how you can actually
> return the value?
> I think compiler must give error. How could you compile it?
Returning void values is a GNU extension. I've seen it in a few
places in the kernel. Although in general I'd prefer it we'd remove
it (and have the compiler warn about it).
--
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