On Mon, Nov 05, 2012 at 09:51:19AM +0400, Vladimir Murzin wrote:
> I've not tried your module, but I suppose that you should get warning
> as soon as you try to take write semaphore once again.
>
Thank you for your mail. I wanted to try what you've suggested, but now I'm
facing a different problem.
problem.
-Anand Moon
From: Vladimir Murzin
To: Kumar amit mehta
Cc: Srivatsa Bhat ; kernelnewbies@kernelnewbies.org
Sent: Monday, November 5, 2012 11:21 AM
Subject: Re: Tools for checking incorrect usage of locking techniques in k-space
On Tue, Oct 30, 2012
On Tue, Oct 30, 2012 at 9:41 AM, Kumar amit mehta wrote:
> On Mon, Oct 29, 2012 at 12:03:08AM +0530, Srivatsa Bhat wrote:
>> You'll need CONFIG_LOCKDEP=y as well. An easy way to configure lock debugging
>> checks is to run 'make menuconfig' and enable the required options under the
>> "Kernel hack
On Mon, Oct 29, 2012 at 12:03:08AM +0530, Srivatsa Bhat wrote:
> You'll need CONFIG_LOCKDEP=y as well. An easy way to configure lock debugging
> checks is to run 'make menuconfig' and enable the required options under the
> "Kernel hacking" section.
>
> >
> > If above configuration is all that I n
Hi,
On Sun, Oct 28, 2012 at 12:36 AM, Kumar amit mehta wrote:
> Thank you Srivatsa. It seems that lockdep framework is enabled on my running
> kernel.
>
>
> amit@ubuntu:/boot$ egrep -i "debug_kernel|lockdep" config-3.2.0-29-generic-pae
> CONFIG_LOCKDEP_SUPPORT=y
> CONFIG_DEBUG_KERNEL=y
You'll n
On Sat, Oct 27, 2012 at 09:26:51PM +0530, Srivatsa Bhat wrote:
> On Sat, Oct 27, 2012 at 10:11 AM, Kumar amit mehta
> wrote:
> > Hi,
> >
> > I recently came across this tool called KEDR[1] for checking memory leak in
> > kernel modules. I'm using it to check If my trivial kernel modules (based on
Hi,
On Sat, Oct 27, 2012 at 10:11 AM, Kumar amit mehta wrote:
> Hi,
>
> I recently came across this tool called KEDR[1] for checking memory leak in
> kernel modules. I'm using it to check If my trivial kernel modules (based on
> LDD3 examples) are leaking memory. I was wondering if there exist a
