From: Alan Cox <alan@linux.intel.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ming Lei <tom.leiming@gmail.com>, Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: 3.4+ tty lockdep trace
Date: Thu, 24 May 2012 15:54:57 +0100 [thread overview]
Message-ID: <20120524155457.56e37df2@bob.linux.org.uk> (raw)
In-Reply-To: <CA+1xoqeD3yyOgmLe_eQ_PS=HJA=93Syidtk6rq-K9dBoC-DOzQ@mail.gmail.com>
On Thu, 24 May 2012 13:24:56 +0200
Sasha Levin <levinsasha928@gmail.com> wrote:
> On Thu, May 24, 2012 at 1:21 PM, Sasha Levin
> <levinsasha928@gmail.com> wrote:
> > On Thu, May 24, 2012 at 1:20 PM, Sasha Levin
> > <levinsasha928@gmail.com> wrote:
> >> On Thu, May 24, 2012 at 1:10 PM, Alan Cox
> >> <alan@lxorguk.ukuu.org.uk> wrote:
> >>>> I'm still seeing the warning with this patch:
> >>>
> >>> Can you attach the trace that went with the trigger as well ?
> >>
> >> Ofcourse, attached as a file.
> >
> > Heh, this was a different one as well. I'll try to get the one I got
> > in the morning again.
>
> And here is the second one attached as well, so these are two
> different warnings I get with the new version.
I'm somewhat baffled by this one. Can lockdep be fooled by an object
being freed and reallocated at the same address, Is there any markup
that should be present to avoid that ?
Alan
next prev parent reply other threads:[~2012-05-24 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 0:26 3.4+ tty lockdep trace Dave Jones
2012-05-23 1:06 ` Ming Lei
2012-05-23 1:17 ` Dave Jones
2012-05-23 2:02 ` Dave Jones
2012-05-23 2:44 ` Ming Lei
2012-05-23 23:05 ` Alan Cox
2012-05-24 6:13 ` Sasha Levin
2012-05-24 11:10 ` Alan Cox
2012-05-24 11:20 ` Sasha Levin
2012-05-24 11:21 ` Sasha Levin
2012-05-24 11:24 ` Sasha Levin
2012-05-24 14:54 ` Alan Cox [this message]
2012-05-25 2:32 ` Steven Rostedt
2012-05-25 8:07 ` Sasha Levin
2012-05-25 8:30 ` Ming Lei
2012-05-25 10:24 ` Sasha Levin
2012-05-25 11:02 ` Alan Cox
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=20120524155457.56e37df2@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox