Linux EXT4 FS development
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16312] New: WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty
Date: Mon, 28 Jun 2010 17:47:47 GMT	[thread overview]
Message-ID: <bug-16312-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=16312

           Summary: WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.35-rc3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: maciej.rutecki@gmail.com
                CC: rjw@sisk.pl, maciej.rutecki@gmail.com,
                    zdenek.kabelac@gmail.com
        Regression: Yes


Subject    : WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty
Submitter  : Zdenek Kabelac <zdenek.kabelac@gmail.com>
Date       : 2010-06-28 9:40
Message-ID : AANLkTin24fr5O4_q5Xbo9Y_NKkEmtcp6Hgmr9_4qXaFz@mail.gmail.com
References : http://marc.info/?l=linux-kernel&m=127771804806465&w=2

This entry is being used for tracking a regression from 2.6.34.  Please don't
close it until the problem is fixed in the mainline.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2010-06-28 17:47 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 17:47 bugzilla-daemon [this message]
2010-06-28 17:48 ` [Bug 16312] WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty bugzilla-daemon
2010-07-09  2:23 ` bugzilla-daemon
2010-07-09 21:33 ` bugzilla-daemon
2010-07-23 15:30 ` bugzilla-daemon
2010-07-23 20:11 ` bugzilla-daemon
2010-07-26 13:01 ` bugzilla-daemon
2010-07-26 13:02 ` bugzilla-daemon
2010-07-26 13:05 ` bugzilla-daemon
2010-07-26 13:59 ` bugzilla-daemon
2010-07-26 17:53 ` bugzilla-daemon
2010-07-26 19:56 ` bugzilla-daemon
2010-07-27 11:54 ` bugzilla-daemon
2010-07-27 11:55 ` bugzilla-daemon
2010-07-27 14:20 ` bugzilla-daemon
2010-07-27 15:03 ` bugzilla-daemon
2010-07-27 15:04 ` bugzilla-daemon
2010-07-27 15:23 ` bugzilla-daemon
2010-07-27 15:36 ` bugzilla-daemon
2010-07-27 18:06 ` bugzilla-daemon
2010-07-29 19:29 ` bugzilla-daemon
2010-07-29 19:38 ` bugzilla-daemon
2010-07-29 19:38 ` bugzilla-daemon
2010-08-01 19:40 ` bugzilla-daemon
2010-08-02 13:21 ` bugzilla-daemon
2010-08-05 12:12 ` bugzilla-daemon
2010-08-05 18:07 ` bugzilla-daemon
2010-08-05 18:31 ` bugzilla-daemon
2010-08-06  6:32 ` bugzilla-daemon
2010-08-20 22:23 ` bugzilla-daemon
2010-09-08  7:44 ` bugzilla-daemon
2010-09-08  8:24 ` bugzilla-daemon
2010-09-13 17:56 ` bugzilla-daemon
2010-09-16 18:13 ` bugzilla-daemon
2010-09-16 18:15 ` bugzilla-daemon
2010-09-16 18:16 ` bugzilla-daemon
2010-09-16 18:39 ` bugzilla-daemon
2010-09-17  0:18 ` bugzilla-daemon
2010-09-20 10:20 ` bugzilla-daemon
2010-10-03 10:05 ` bugzilla-daemon
2010-10-03 10:25 ` bugzilla-daemon
2010-10-03 20:14 ` bugzilla-daemon
2010-10-04 21:10 ` bugzilla-daemon
2011-01-23 16:09 ` bugzilla-daemon

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=bug-16312-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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