mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: Jan Kara <jack@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: BUG on fs/inode.c:1442 (linux 3.3.1 and 3.3.2)
Date: Wed, 9 May 2012 12:44:46 +0200	[thread overview]
Message-ID: <20120509104446.GB5092@quack.suse.cz> (raw)
In-Reply-To: <20120506123100.GI1927@vicerveza.homeunix.net>

On Sun 06-05-12 14:31:00, Lluís Batlle i Rossell wrote:
> On Wed, Apr 18, 2012 at 01:48:44PM +0200, Jan Kara wrote:
> >   Hello,
> > 
> > On Sun 15-04-12 23:56:01, Lluís Batlle i Rossell wrote:
> > > destroying my openvpn client connection (SIGINT to openvp), in linux 3.3.1 and
> > > now also in 3.3.2, I noticed this BUG in dmesg (attached).
> > > 
> > > It's a vanilla 3.3.2, at this shot.
> > > 
> > > I know it never happened to me in any 3.2, but I did not try 3.3.0.
> > > 
> > > I attach the .config. And I have the debug info for this kernel too, if this
> > > helps someone find a fix. But I imagine it's easy to reproduce.
> >   From the first look it would seem as use after free bug but can you
> > please post disassembly of iput() function from your kernel? I.e. you load
> > vmlinux in gdb and run 'disass iput'. Thanks.
> 
> Sorry for the delay. Here it is, for 3.3.2:
  Thanks for the disassembly. I was hoping that the contents of
inode->i_state would be loaded in some register so we can see what value
it has. Sadly that's not the case so I cannot say anything more.

Did the bug happen to you again after the original report?

									Honza

-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2012-05-09 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 21:56 Lluís Batlle i Rossell
2012-04-18 11:48 ` Jan Kara
2012-05-06 12:31   ` Lluís Batlle i Rossell
2012-05-09 10:44     ` Jan Kara [this message]

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=20120509104446.GB5092@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viric@viric.name \
    /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

all inboxes | Powered by JetHome®