All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>, LinMa <linma@zju.edu.cn>
Subject: Re: [PATCH] Bluetooth: reorganize functions from hci_sock_sendmsg()
Date: Mon, 23 Aug 2021 14:03:56 -0700	[thread overview]
Message-ID: <CABBYNZKcFsk1SroWcP=SVMwFAJongtVG=gc9DK=SoRLvTCOwCQ@mail.gmail.com> (raw)
In-Reply-To: <246902bb-aafa-43bf-bf7c-ff26bfed5be1@i-love.sakura.ne.jp>

Hi Tetsuo,

On Sun, Aug 22, 2021 at 8:42 AM Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
>
> On 2021/07/24 6:44, Luiz Augusto von Dentz wrote:
> > Hi Tetsuo,
> >
> > On Thu, Jul 22, 2021 at 12:42 AM Tetsuo Handa
> > <penguin-kernel@i-love.sakura.ne.jp> wrote:
> >>
> >> Since userfaultfd mechanism allows sleeping with kernel lock held,
> >> avoiding page fault with kernel lock held where possible will make
> >> the module more robust. This patch just brings memcpy_from_msg() calls
> >> to out of sock lock.
> >>
> >> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> >
> > Reviewed-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> >
>
> Can this patch go to v5.15 ?

Applied, thanks. I will be sending another pull-request by the end of
this week which shall include it.

-- 
Luiz Augusto von Dentz

      reply	other threads:[~2021-08-23 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22  7:42 [PATCH] Bluetooth: reorganize functions from hci_sock_sendmsg() Tetsuo Handa
2021-07-22  9:09 ` bluez.test.bot
2021-07-23 21:44 ` [PATCH] " Luiz Augusto von Dentz
2021-08-22 15:42   ` Tetsuo Handa
2021-08-23 21:03     ` Luiz Augusto von Dentz [this message]

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='CABBYNZKcFsk1SroWcP=SVMwFAJongtVG=gc9DK=SoRLvTCOwCQ@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linma@zju.edu.cn \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /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.