All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anjali Kulkarni <anjali.k.kulkarni@oracle.com>
To: Christian Brauner <brauner@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
	"edumazet@google.com" <edumazet@google.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"zbr@ioremap.net" <zbr@ioremap.net>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"ecree.xilinx@gmail.com" <ecree.xilinx@gmail.com>,
	"leon@kernel.org" <leon@kernel.org>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"socketcan@hartkopp.net" <socketcan@hartkopp.net>,
	"petrm@nvidia.com" <petrm@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v1 2/5] connector/cn_proc: Add filtering to fix some bugs
Date: Tue, 14 Mar 2023 18:51:07 +0000	[thread overview]
Message-ID: <BY5PR10MB412905AE523693D8D8A62669C4BE9@BY5PR10MB4129.namprd10.prod.outlook.com> (raw)
In-Reply-To: <20230314083843.wb3xmzboejxfg73b@wittgenstein>



________________________________________
From: Christian Brauner <brauner@kernel.org>
Sent: Tuesday, March 14, 2023 1:38 AM
To: Jakub Kicinski
Cc: Anjali Kulkarni; davem@davemloft.net; edumazet@google.com; pabeni@redhat.com; zbr@ioremap.net; johannes@sipsolutions.net; ecree.xilinx@gmail.com; leon@kernel.org; keescook@chromium.org; socketcan@hartkopp.net; petrm@nvidia.com; linux-kernel@vger.kernel.org; netdev@vger.kernel.org
Subject: Re: [PATCH v1 2/5] connector/cn_proc: Add filtering to fix some bugs

On Mon, Mar 13, 2023 at 05:24:41PM -0700, Jakub Kicinski wrote:
> On Fri, 10 Mar 2023 14:15:44 -0800 Anjali Kulkarni wrote:
> > diff --git a/include/linux/connector.h b/include/linux/connector.h
> > index 487350bb19c3..1336a5e7dd2f 100644
> > --- a/include/linux/connector.h
> > +++ b/include/linux/connector.h
> > @@ -96,7 +96,11 @@ void cn_del_callback(const struct cb_id *id);
> >   *
> >   * If there are no listeners for given group %-ESRCH can be returned.
> >   */
> > -int cn_netlink_send_mult(struct cn_msg *msg, u16 len, u32 portid, u32 group, gfp_t gfp_mask);
> > +int cn_netlink_send_mult(struct cn_msg *msg, u16 len, u32 portid,
> > +                    u32 group, gfp_t gfp_mask,
> > +                    int (*filter)(struct sock *dsk, struct sk_buff *skb,
> > +                                  void *data),
> > +                    void *filter_data);
>
> kdoc needs to be extended

just a thought from my side. I think giving access to unprivileged users
will require a little thought as that's potentially sensitive.

If possible I would think that the patches that don't lead to a
behavioral change should go in completely independently and then we can
discuss the non-root access change.
ANJALI> That sounds fine. I can send the non-root change as the last patch 
in the series. I can also add a change to allow the sensitive content only if
the user ID or parent ID matches etc. I know the exit status needs more
discussion..

  reply	other threads:[~2023-03-14 18:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 22:15 [PATCH v1 0/5] Process connector bug fixes & enhancements Anjali Kulkarni
2023-03-10 22:15 ` [PATCH v1 1/5] netlink: Reverse the patch which removed filtering Anjali Kulkarni
2023-03-10 22:15 ` [PATCH v1 2/5] connector/cn_proc: Add filtering to fix some bugs Anjali Kulkarni
2023-03-14  0:24   ` Jakub Kicinski
2023-03-14  2:32     ` Anjali Kulkarni
2023-03-15  4:59       ` Jakub Kicinski
2023-03-15 19:08         ` Anjali Kulkarni
2023-03-15 19:13           ` Anjali Kulkarni
2023-03-15 19:50           ` Jakub Kicinski
2023-03-15 20:12             ` Anjali Kulkarni
2023-03-14  8:38     ` Christian Brauner
2023-03-14 18:51       ` Anjali Kulkarni [this message]
2023-04-01 18:32       ` Anjali Kulkarni
2023-03-10 22:15 ` [PATCH v1 3/5] connector/cn_proc: Test code for proc connector Anjali Kulkarni
2023-03-10 22:15 ` [PATCH v1 4/5] connector/cn_proc: Allow non-root users access Anjali Kulkarni
2023-03-10 22:15 ` [PATCH v1 5/5] connector/cn_proc: Performance improvements Anjali Kulkarni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BY5PR10MB412905AE523693D8D8A62669C4BE9@BY5PR10MB4129.namprd10.prod.outlook.com \
    --to=anjali.k.kulkarni@oracle.com \
    --cc=brauner@kernel.org \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=johannes@sipsolutions.net \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=socketcan@hartkopp.net \
    --cc=zbr@ioremap.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.