public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Jorge Bastos <mysql.jorge@decimal.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs.c bug in 3.2-rc5
Date: Tue, 13 Dec 2011 19:07:07 +0100	[thread overview]
Message-ID: <20111213180707.GI11747@quack.suse.cz> (raw)
In-Reply-To: <43556.213.228.140.150.1323560920.squirrel@webmail.decimal.pt>

  Hello,

On Sat 10-12-11 23:48:40, Jorge Bastos wrote:
> Have a VM in hyper-v, and with 3.2x reiserfs.c crashes.
> Attached there's the images, since I'm unable to copy text only.
> 
> What can be done here?
  The assertion failing is:
        BUG_ON(nblocks > journal->j_trans_max);
in do_journal_begin_r(). That means that reiserfs_create() tried to start a
transaction with more credits than allowed by the journal.

  When did you started to see this problem? Also do you use SELinux (or
generally security labels)?

								Honza

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

  reply	other threads:[~2011-12-13 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 23:48 Reiserfs.c bug in 3.2-rc5 Jorge Bastos
2011-12-13 18:07 ` Jan Kara [this message]
2011-12-24 11:55   ` Jorge Bastos
2012-01-02 11:52     ` Jan Kara
     [not found]       ` <005301ccc998$201c9da0$6055d8e0$@jorge@decimal.pt>
2012-01-03  1:08         ` Jan Kara
     [not found]           ` <000701ccc9fa$74df73f0$5e9e5bd0$@jorge@decimal.pt>
2012-01-03 12:38             ` Jan Kara
2012-01-03 15:25               ` Mimi Zohar
2012-01-03 16:48                 ` Linus Torvalds
2012-01-03 18:45                   ` Mimi Zohar
2012-01-03 19:17                     ` Linus Torvalds
2012-01-03 22:28                       ` Mimi Zohar
2012-01-03 23:47                     ` James Morris
2012-01-04  0:18                       ` Linus Torvalds
2012-01-04  1:02                         ` James Morris
2012-01-04 17:15                         ` Jan Kara

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=20111213180707.GI11747@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mysql.jorge@decimal.pt \
    /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