All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/4] Bluetooth: Add bt_skb_sendmsg helper
Date: Wed, 1 Sep 2021 07:44:48 +0200	[thread overview]
Message-ID: <9067109F-D8FD-47E9-AD02-FB6B7DFFDB3E@holtmann.org> (raw)
In-Reply-To: <20210901002621.414016-1-luiz.dentz@gmail.com>

Hi Luiz,

> bt_skb_sendmsg helps takes care of allocation the skb and copying the
> the contents of msg over to the skb while checking for possible errors
> so it should be safe to call it without holding lock_sock.
> 
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> ---
> include/net/bluetooth/bluetooth.h | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> 
> diff --git a/include/net/bluetooth/bluetooth.h b/include/net/bluetooth/bluetooth.h
> index 9125effbf448..f858efcf9f40 100644
> --- a/include/net/bluetooth/bluetooth.h
> +++ b/include/net/bluetooth/bluetooth.h
> @@ -420,6 +420,32 @@ static inline struct sk_buff *bt_skb_send_alloc(struct sock *sk,
> 	return NULL;
> }
> 
> +/* Shall not be called with lock_sock held */
> +static inline struct sk_buff *bt_skb_sendmsg(struct sock *sk,
> +					     struct msghdr *msg,
> +					     size_t len, size_t header,
> +					     size_t footer)
> +{
> +	struct sk_buff *skb;
> +	int err;
> +
> +	skb = bt_skb_send_alloc(sk, len + header + footer,
> +				msg->msg_flags & MSG_DONTWAIT, &err);
> +	if (!skb)
> +		return ERR_PTR(err);
> +
> +	skb_reserve(skb, header);

I am not with you on this one since bt_skb_send_alloc already calls skb_reserve in the first place.

/**                                                                              
 *      skb_reserve - adjust headroom                                            
 *      @skb: buffer to alter                                                    
 *      @len: bytes to move                                                      
 *                                                                               
 *      Increase the headroom of an empty &sk_buff by reducing the tail          
 *      room. This is only allowed for an empty buffer.                          
 */

In addition we have this comment here. So what kind of headroom do we need with this SKB?

And wouldn’t it be better to actually assign a tailroom instead of just a large enough buffer?

/**                                                                              
 *      skb_tailroom_reserve - adjust reserved_tailroom                          
 *      @skb: buffer to alter                                                    
 *      @mtu: maximum amount of headlen permitted                                
 *      @needed_tailroom: minimum amount of reserved_tailroom                    
 *                                                                               
 *      Set reserved_tailroom so that headlen can be as large as possible but    
 *      not larger than mtu and tailroom cannot be smaller than                  
 *      needed_tailroom.                                                         
 *      The required headroom should already have been reserved before using     
 *      this function.                                                           
 */              

We also have this capability inside the SKBs.

So while the basic idea of this patchset seems fine, we need to figure out the details and not overload us in spaghetti code by wanting to have a common bt_skb_* helper. Maybe it is actually not helpful in this case since we just have to have a too large parameter list to satisfy all 3 users.

Regards

Marcel


  parent reply	other threads:[~2021-09-01  5:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  0:26 [PATCH 1/4] Bluetooth: Add bt_skb_sendmsg helper Luiz Augusto von Dentz
2021-09-01  0:26 ` [PATCH 2/4] Bluetooth: Add bt_skb_sendmmsg helper Luiz Augusto von Dentz
2021-09-01  0:26 ` [PATCH 3/4] Bluetooth: SCO: Replace use of memcpy_from_msg with bt_skb_sendmsg Luiz Augusto von Dentz
2021-09-01  0:26 ` [PATCH 4/4] Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg Luiz Augusto von Dentz
2021-09-03  9:02   ` [Bluetooth] e1ce6a3427: BUG:unable_to_handle_page_fault_for_address kernel test robot
2021-09-03  9:02     ` kernel test robot
2021-09-01  2:02 ` [1/4] Bluetooth: Add bt_skb_sendmsg helper bluez.test.bot
2021-09-01  5:44 ` Marcel Holtmann [this message]
2021-09-01 19:16   ` [PATCH 1/4] " Luiz Augusto von Dentz

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=9067109F-D8FD-47E9-AD02-FB6B7DFFDB3E@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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.