[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201009270340.26148.pavel@pavlinux.ru>
Date: Mon, 27 Sep 2010 03:40:17 +0400
From: Pavel Vasilyev <pavel@...linux.ru>
To: "Rafael J. Wysocki" <rjw@...k.pl>, linux-kernel@...r.kernel.org
Subject: Re: [Bug #19082] fs/fs-writeback.c to dump
В сообщении от Понедельник 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@...linux.ru>
> Date : 2010-09-25 15:52 (2 days old)
> Message-ID : <201009251952.58749.pavel@...linux.ru>
> References : http://marc.info/?l=linux-kernel&m=128543035026659&w=2
Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists