All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Straube <straube.linux@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Phillip Potter <phil@philpotter.co.uk>,
	"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: staging: r8188eu: how to handle nested mutex under spinlock
Date: Mon, 4 Apr 2022 16:16:31 +0200	[thread overview]
Message-ID: <66efc2d7-ec85-25af-1499-0dce2a09c3cd@gmail.com> (raw)
In-Reply-To: <20220404133312.GC3293@kadam>

On 4/4/22 15:33, Dan Carpenter wrote:
> On Sun, Apr 03, 2022 at 02:18:04PM +0200, Michael Straube wrote:
>> On 4/3/22 14:10, Fabio M. De Francesco wrote:
>>> For a list of all the paths to a given function you may use Smatch:
>>>
>>> ./smatch/smatch_data/db/smdb.py ips_leave
>>>
>>> or
>>>
>>> ./smatch/smatch_data/db/smdb.py call_tree ips_leave
>>>
>>> But perhaps you already know how to do it.
>>
>> Yes, but thank you anyway. :)
>>
> 
> My email (gmail account) has been so weird recently.  I don't know why
> I'm not getting Fabio's emails...  Presumably they will show up in a few
> days.
> 
> The other command to use is:
> 
> $ ./smatch/smatch_data/db/smdb.py preempt ips_leave
> rtw_set_802_11_disassociate() <- disables preempt
> -> _rtw_pwr_wakeup()
>     -> LeaveAllPowerSaveMode()
>        -> ips_leave()
> 
> I save that to a file, open it with with vim and run a vim function
> `hall` (for highlight all) from my .vimrc file.
> 
> " Use :hall to highlight all the words in a file (for debugging sleeping bugs)
> function HLall()
>    let a=[]
>    %s/\w\+/\=add(a, submatch(0))/gn
>    let @/ = join(a, "\\|")
> endfunction
> cnoreabbrev hall call HLall() <CR>:set hls<CR>
> 
> That highlights all the functions is the call tree, then I use cscope to
> jump to rtw_set_802_11_disassociate and follow the highlighted functions
> to ips_leave().

Thank you for this hint Dan. :)

thanks,
Michael


  reply	other threads:[~2022-04-04 14:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02 20:47 staging: r8188eu: how to handle nested mutex under spinlock Michael Straube
2022-04-02 21:13 ` Pavel Skripkin
2022-04-02 21:32 ` Larry Finger
2022-04-03  8:44   ` Michael Straube
     [not found] ` <4389354.LvFx2qVVIh@leap>
     [not found]   ` <1813843.tdWV9SEqCh@leap>
2022-04-03 11:08     ` Michael Straube
     [not found]       ` <7365301.EvYhyI6sBW@leap>
2022-04-03 11:41         ` Michael Straube
2022-04-03 11:48           ` Pavel Skripkin
     [not found]             ` <1817830.CQOukoFCf9@leap>
2022-04-03 12:14               ` Michael Straube
2022-04-03 12:19             ` Pavel Skripkin
     [not found]               ` <4412825.cEBGB3zze1@leap>
2022-04-03 12:45                 ` Pavel Skripkin
     [not found]                   ` <2029549.KlZ2vcFHjT@leap>
2022-04-03 13:02                     ` Pavel Skripkin
2022-04-03 20:51                       ` Michael Straube
2022-04-03 21:15                         ` Pavel Skripkin
2022-04-04  8:50                           ` David Laight
2022-04-04 16:38                             ` Pavel Skripkin
2022-04-04 16:59                               ` David Laight
2022-04-04 17:12                                 ` Pavel Skripkin
     [not found]           ` <1858641.taCxCBeP46@leap>
     [not found]             ` <2366209.jE0xQCEvom@leap>
2022-04-03 12:18               ` Michael Straube
2022-04-04 13:33                 ` Dan Carpenter
2022-04-04 14:16                   ` Michael Straube [this message]
     [not found]         ` <3097543.5fSG56mABF@leap>
2022-04-03 11:44           ` Michael Straube

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=66efc2d7-ec85-25af-1499-0dce2a09c3cd@gmail.com \
    --to=straube.linux@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dan.carpenter@oracle.com \
    --cc=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=phil@philpotter.co.uk \
    /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.