From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Ts'o Subject: Re: [PATCH 1/5] fs: add netlink notification interface Date: Fri, 19 Aug 2011 11:15:28 -0400 Message-ID: <20110819151528.GB4602@thunk.org> References: <1313669906-14931-1-git-send-email-lczerner@redhat.com> <1313669906-14931-2-git-send-email-lczerner@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Alexander Viro To: Lukas Czerner Return-path: Received: from li9-11.members.linode.com ([67.18.176.11]:58330 "EHLO test.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752855Ab1HSPPc (ORCPT ); Fri, 19 Aug 2011 11:15:32 -0400 Content-Disposition: inline In-Reply-To: <1313669906-14931-2-git-send-email-lczerner@redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Aug 18, 2011 at 02:18:22PM +0200, Lukas Czerner wrote: > +void fs_nl_send_warning(dev_t dev, unsigned int warntype) > +{ I'm pretty sure this interface isn't going to be sufficient in the long run. I can imagine that people might want to pass in a struct inode *, or a struct file * if available, so we could pass back the inode number involved, or even the pathname. Also, I'd suggesting changing "warning" to "error", since that's what most of the things we are sending really are... > + ret = nla_put_u32(skb, FS_NL_A_WARNING, warntype); > + if (ret) > + goto attr_err_out; Why not make the warning type to be a string instead of an integer? This would make it easier to extend the protocol in the future. > + ret = nla_put_u64(skb, FS_NL_A_CAUSED_ID, current_uid()); > + if (ret) > + goto attr_err_out; I'd also suggest passing back the process id that requested the I/O if that's known... - Ted