lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinKnHs=oV+7wJdSZcNHTyMmWgPiEev6bBmL==R9@mail.gmail.com>
Date:	Tue, 1 Feb 2011 10:45:16 +0530
From:	Rajat Sharma <fs.rajat@...il.com>
To:	Sri Ram Vemulpali <sri.ram.gmu06@...il.com>
Cc:	Kernel-newbies <kernelnewbies@...linux.org>,
	linux-kernel-mail <linux-kernel@...r.kernel.org>
Subject: Re: what is spinlock depth

lockdep finds out dependency in locking order at runtime. More on this
in kernel documentation linux/Documentation/lockdep-design.txt

Rajat

On Tue, Feb 1, 2011 at 1:57 AM, Sri Ram Vemulpali
<sri.ram.gmu06@...il.com> wrote:
> Hi all,
>
> I am reading spinlock code and looking at struct raw_spinlock. I found
> struct lockdep_map as member.
> which is defined as
>
> struct lockdep_map {
>       struct lock_class_key           *key;
>       struct lock_class               *class_cache[NR_LOCKDEP_CACHING_CLASSES];
>       const char                      *name;
> #ifdef CONFIG_LOCK_STAT
>       int                             cpu;
>      unsigned long                   ip;
> #endif
> };
>
> Can anyone help me explain, how this struct helps the spinlock. Why do
> we need lockdepth.
> Thanks for help in advance.
> --
> Regards,
> Sri.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@...nelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ