All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Martin Grothe <martin.grothe@rub.de>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: kernel smp.c functions not called by Bluetootl LE controller
Date: Thu, 20 Jul 2017 20:24:50 +0200	[thread overview]
Message-ID: <19307C37-EF03-4E42-AFAD-06855DCB7A3F@holtmann.org> (raw)
In-Reply-To: <38d8a549-4335-cf0b-9273-d9ef9b51ac0b@rub.de>

Hi Martin,

> I try to call printk (with priority KERN_ALERT) functions placed in the
> net/bluetooth/smp.c file of my linux kernel 4.9.35 in order to get
> output from specifc functions like:
> 
> static int smp_cmd_public_key()
> 
> But during a pairing with another bluetooth LE device the output of
> these function is never shown in /var/log/kern.log
> 
> Is there any way to verify, that the LE Controller accesses the Security
> Manager Protocol source code the Linux Kernel?
> 
> As far as I understood the Core Specification, in BT 4.0 an above the
> Security Manager is always integrated in the Link Manager, when it comes
> to BR/EDR. But for LE the SM is integrated in the Host part and not the
> Controller. Thus LE Controller should access the smp.c in the Linux kernel.

just run btmon and you see all the security manager exchanges.

Regards

Marcel


  reply	other threads:[~2017-07-20 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 12:59 kernel smp.c functions not called by Bluetootl LE controller Martin Grothe
2017-07-20 18:24 ` Marcel Holtmann [this message]
2017-07-21 11:17   ` Martin Grothe
2017-07-21 11:29     ` Marcel Holtmann
2017-07-21 11:41       ` Marcel Holtmann
2017-07-21 11:44         ` Martin Grothe
2017-07-21 11:49           ` Marcel Holtmann

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=19307C37-EF03-4E42-AFAD-06855DCB7A3F@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=martin.grothe@rub.de \
    /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.