mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Vasilyev <pavel@pavlinux.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>, linux-kernel@vger.kernel.org
Subject: Re: [Bug #19082] fs/fs-writeback.c to dump
Date: Mon, 27 Sep 2010 03:40:17 +0400	[thread overview]
Message-ID: <201009270340.26148.pavel@pavlinux.ru> (raw)
In-Reply-To: <sQALkqF1FWE.A.ztD.Xo6nMB@chimera>

[-- Attachment #1: Type: Text/Plain, Size: 1709 bytes --]

В сообщении от Понедельник 27 сентября 2010 00:04:16 вы написали:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
> 
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the
> tracking team know (either way).

I don't know, this bug or not :)

# view +73 fs/fs-writeback.c
...

static inline struct backing_dev_info *inode_to_bdi(struct inode *inode)
{
        struct super_block *sb = inode->i_sb;
        struct backing_dev_info *bdi = inode->i_mapping->backing_dev_info;

        /*
         * For inodes on standard filesystems, we use superblock's bdi. For
         * inodes on virtual filesystems, we want to use inode mapping's bdi
         * because they can possibly point to something useful (think about
         * block_dev filesystem).
         */

        if (sb->s_bdi && sb->s_bdi != &noop_backing_dev_info) {

               /* Some device inodes could play dirty tricks. Catch them... */

          WARN(bdi != sb->s_bdi && bdi_cap_writeback_dirty(bdi),
                        "Dirtiable inode bdi %s != sb bdi %s\n",
                        bdi->name, sb->s_bdi->name);
                return sb->s_bdi;
        }
        return bdi;
}




> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19082
> Subject		: fs/fs-writeback.c to dump
> Submitter	: Pavel Vasilyev <pavel@pavlinux.ru>
> Date		: 2010-09-25 15:52 (2 days old)
> Message-ID	: <201009251952.58749.pavel@pavlinux.ru>
> References	: http://marc.info/?l=linux-kernel&m=128543035026659&w=2

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-09-26 23:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 19:55 2.6.36-rc5-git7: Reported regressions from 2.6.35 Rafael J. Wysocki
2010-09-26 19:55 ` [Bug #16951] hackbench regression with 2.6.36-rc1 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #16971] qla4xxx compile failure on 32-bit PowerPC: missing readq and writeq Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access Rafael J. Wysocki
2010-10-02 16:52   ` Ted Ts'o
2010-10-03 11:21     ` Vegard Nossum
2010-09-26 20:04 ` [Bug #17061] 2.6.36-rc1 on zaurus: bluetooth regression Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17121] Two blank rectangles more than 10 cm long when booting Rafael J. Wysocki
2010-09-27  6:01   ` Eric Valette
2010-09-27 19:41     ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18962] screen failes in kde Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #17722] 2.6.36-rc3: WARNING: at net/mac80211/scan.c:269 ieee80211_scan_completed Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18342] [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18742] PROBLEM: Kernel panic on 2.6.36-rc4 when loading intel_ips on Core i3 laptop Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19072] [2.6.36-rc regression] occasional complete system hangs on sparc64 SMP Rafael J. Wysocki
2010-09-27 10:28   ` Mikael Pettersson
2010-09-27 19:43     ` Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19002] Radeon rv730 AGP/KMS/DRM kernel lockup Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs Rafael J. Wysocki
2010-10-02 16:54   ` Ted Ts'o
2010-10-02 21:58     ` Rafael J. Wysocki
2010-10-03  2:27       ` Ted Ts'o
2010-10-03 15:16         ` Tejun Heo
2010-10-04  9:59           ` Jan Kara
2010-10-04 10:12             ` Christoph Hellwig
2010-10-04 17:46               ` Jens Axboe
2010-10-04 20:09       ` Andrew Morton
2010-10-05 15:59         ` Ted Ts'o
2010-09-26 20:04 ` [Bug #19052] 2.6.36-rc5-git1 -- [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #18992] warn_slow_path_common in iwlagn/mac80211 in 2.6.36-rc5 Rafael J. Wysocki
2010-09-26 20:04 ` [Bug #19082] fs/fs-writeback.c to dump Rafael J. Wysocki
2010-09-26 23:40   ` Pavel Vasilyev [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=201009270340.26148.pavel@pavlinux.ru \
    --to=pavel@pavlinux.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

Powered by JetHome