diff for duplicates of <1285767616.2437.142.camel@localhost> diff --git a/a/1.txt b/N1/1.txt index b79ba68..08efd20 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,39 +4,27 @@ On Wed, 2010-09-29 at 15:00 +0200, Jan Kara wrote: > > > On Tue, Sep 28, 2010 at 12:25:48AM +0200, Jan Kara wrote: > > > > [Added CCs for similar ecryptfs warning] > > > > On Thu 23-09-10 12:38:49, Andrew Morton wrote: -> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; i= -t did not=20 -> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does= - not have=20 -> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which intro= -duces the=20 +> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; it did not +> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does not have +> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which introduces the > > > > > > warning. > > > > > > [...] -> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transi= -d 22342=20 +> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transid 22342 > > > > > > /dev/mapper/vg_cesarbinspiro-lv_home > > > > > > SELinux: initialized (dev dm-3, type btrfs), uses xattr > > > > > > ------------[ cut here ]------------ > > > > > > WARNING: at fs/fs-writeback.c:87 inode_to_bdi+0x62/0x6d() > > > > > > Hardware name: Inspiron N4010 -> > > > > > Dirtiable inode bdi default !=3D sb bdi btrfs -> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb=20 -> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hd= -a_intel=20 -> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev = -snd_seq=20 -> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl3= -2 btusb=20 -> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi del= -l_laptop snd=20 -> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_= -page_alloc=20 -> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd= - aes_x86_64=20 -> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_= -helper drm=20 -> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wai= -t_scan] +> > > > > > Dirtiable inode bdi default != sb bdi btrfs +> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb +> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hda_intel +> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev snd_seq +> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl32 btusb +> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi dell_laptop snd +> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_page_alloc +> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd aes_x86_64 +> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_helper drm +> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] > > > > > > Pid: 1073, comm: find Not tainted 2.6.36-rc5+ #8 > > > > > > Call Trace: > > > > > > [<ffffffff8104d0e4>] warn_slowpath_common+0x85/0x9d @@ -48,36 +36,27 @@ t_scan] > > > > > > [<ffffffff8112259b>] vfs_readdir+0x8d/0xb4 > > > > > > [<ffffffff8112270b>] sys_getdents+0x81/0xd1 > > > > > > [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b -> > > > Thanks for the report. These bdi pointers are a mess. As Chri= -s pointed -> > > > out, btrfs forgets to properly initialize inode->i_mapping.back= -ing_dev_info -> > > > for directories and special inodes and thus these were previous= -ly attached -> > > > to default_backing_dev_info which probably isn't what Chris wou= -ld like to +> > > > Thanks for the report. These bdi pointers are a mess. As Chris pointed +> > > > out, btrfs forgets to properly initialize inode->i_mapping.backing_dev_info +> > > > for directories and special inodes and thus these were previously attached +> > > > to default_backing_dev_info which probably isn't what Chris would like to > > > > see. -> > >=20 -> > > There's no actual writeback for these, so it works fine for btrfs= - either +> > > +> > > There's no actual writeback for these, so it works fine for btrfs either > > > way. -> >=20 -> > Side note: every time inode is marked as dirty, we wake up a bdi th= -read +> > +> > Side note: every time inode is marked as dirty, we wake up a bdi thread > > or the default bdi thread. So if we have inodes which do not need > > write-back, we should never mark them as dirty. -> Are you sure? I think we wake up the thread only when it's the firs= -t +> Are you sure? I think we wake up the thread only when it's the first > dirty inode for the bdi... Err, right. If no one ever marks it as clean then we won't wake-up the thread. But I thought that marking it as dirty even once is bad because this causes bdi thread creation, which consumes resources. -Sorry for my ignorance, I did not really follow the conversation, I jus= -t -remember that when I looked at bdi stuff, I noticed that during boot th= -e +Sorry for my ignorance, I did not really follow the conversation, I just +remember that when I looked at bdi stuff, I noticed that during boot the kernel created many bdi threads which were never used then. They eventually exited. But I thought that creating useless bdi threads it about concuming resources and slowing down the boot. @@ -87,13 +66,6 @@ As I remember, the reason was touch_atime() for some of the threads. But really, I did not dig this, I just noticed this conversation and wanted to let you know about the issue I noticed this summer. ---=20 +-- Best Regards, -Artem Bityutskiy (=D0=90=D1=80=D1=82=D1=91=D0=BC =D0=91=D0=B8=D1=82=D1=8E= -=D1=86=D0=BA=D0=B8=D0=B9) - --- -To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = -in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html +Artem Bityutskiy (Артём Битюцкий) diff --git a/a/content_digest b/N1/content_digest index e6a5558..dc0de60 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -30,39 +30,27 @@ "> > > On Tue, Sep 28, 2010 at 12:25:48AM +0200, Jan Kara wrote:\n" "> > > > [Added CCs for similar ecryptfs warning]\n" "> > > > On Thu 23-09-10 12:38:49, Andrew Morton wrote:\n" - "> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; i=\n" - "t did not=20\n" - "> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does=\n" - " not have=20\n" - "> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which intro=\n" - "duces the=20\n" + "> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; it did not \n" + "> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does not have \n" + "> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which introduces the \n" "> > > > > > warning.\n" "> > > > > > [...]\n" - "> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transi=\n" - "d 22342=20\n" + "> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transid 22342 \n" "> > > > > > /dev/mapper/vg_cesarbinspiro-lv_home\n" "> > > > > > SELinux: initialized (dev dm-3, type btrfs), uses xattr\n" "> > > > > > ------------[ cut here ]------------\n" "> > > > > > WARNING: at fs/fs-writeback.c:87 inode_to_bdi+0x62/0x6d()\n" "> > > > > > Hardware name: Inspiron N4010\n" - "> > > > > > Dirtiable inode bdi default !=3D sb bdi btrfs\n" - "> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb=20\n" - "> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hd=\n" - "a_intel=20\n" - "> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev =\n" - "snd_seq=20\n" - "> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl3=\n" - "2 btusb=20\n" - "> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi del=\n" - "l_laptop snd=20\n" - "> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_=\n" - "page_alloc=20\n" - "> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd=\n" - " aes_x86_64=20\n" - "> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_=\n" - "helper drm=20\n" - "> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wai=\n" - "t_scan]\n" + "> > > > > > Dirtiable inode bdi default != sb bdi btrfs\n" + "> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb \n" + "> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hda_intel \n" + "> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev snd_seq \n" + "> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl32 btusb \n" + "> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi dell_laptop snd \n" + "> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_page_alloc \n" + "> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd aes_x86_64 \n" + "> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_helper drm \n" + "> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan]\n" "> > > > > > Pid: 1073, comm: find Not tainted 2.6.36-rc5+ #8\n" "> > > > > > Call Trace:\n" "> > > > > > [<ffffffff8104d0e4>] warn_slowpath_common+0x85/0x9d\n" @@ -74,36 +62,27 @@ "> > > > > > [<ffffffff8112259b>] vfs_readdir+0x8d/0xb4\n" "> > > > > > [<ffffffff8112270b>] sys_getdents+0x81/0xd1\n" "> > > > > > [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b\n" - "> > > > Thanks for the report. These bdi pointers are a mess. As Chri=\n" - "s pointed\n" - "> > > > out, btrfs forgets to properly initialize inode->i_mapping.back=\n" - "ing_dev_info\n" - "> > > > for directories and special inodes and thus these were previous=\n" - "ly attached\n" - "> > > > to default_backing_dev_info which probably isn't what Chris wou=\n" - "ld like to\n" + "> > > > Thanks for the report. These bdi pointers are a mess. As Chris pointed\n" + "> > > > out, btrfs forgets to properly initialize inode->i_mapping.backing_dev_info\n" + "> > > > for directories and special inodes and thus these were previously attached\n" + "> > > > to default_backing_dev_info which probably isn't what Chris would like to\n" "> > > > see.\n" - "> > >=20\n" - "> > > There's no actual writeback for these, so it works fine for btrfs=\n" - " either\n" + "> > > \n" + "> > > There's no actual writeback for these, so it works fine for btrfs either\n" "> > > way.\n" - "> >=20\n" - "> > Side note: every time inode is marked as dirty, we wake up a bdi th=\n" - "read\n" + "> > \n" + "> > Side note: every time inode is marked as dirty, we wake up a bdi thread\n" "> > or the default bdi thread. So if we have inodes which do not need\n" "> > write-back, we should never mark them as dirty.\n" - "> Are you sure? I think we wake up the thread only when it's the firs=\n" - "t\n" + "> Are you sure? I think we wake up the thread only when it's the first\n" "> dirty inode for the bdi...\n" "\n" "Err, right. If no one ever marks it as clean then we won't wake-up the\n" "thread. But I thought that marking it as dirty even once is bad because\n" "this causes bdi thread creation, which consumes resources.\n" "\n" - "Sorry for my ignorance, I did not really follow the conversation, I jus=\n" - "t\n" - "remember that when I looked at bdi stuff, I noticed that during boot th=\n" - "e\n" + "Sorry for my ignorance, I did not really follow the conversation, I just\n" + "remember that when I looked at bdi stuff, I noticed that during boot the\n" "kernel created many bdi threads which were never used then. They\n" "eventually exited. But I thought that creating useless bdi threads it\n" "about concuming resources and slowing down the boot.\n" @@ -113,15 +92,8 @@ "But really, I did not dig this, I just noticed this conversation and\n" "wanted to let you know about the issue I noticed this summer.\n" "\n" - "--=20\n" + "-- \n" "Best Regards,\n" - "Artem Bityutskiy (=D0=90=D1=80=D1=82=D1=91=D0=BC =D0=91=D0=B8=D1=82=D1=8E=\n" - "=D1=86=D0=BA=D0=B8=D0=B9)\n" - "\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-btrfs\" =\n" - "in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + "Artem Bityutskiy (\320\220\321\200\321\202\321\221\320\274 \320\221\320\270\321\202\321\216\321\206\320\272\320\270\320\271)" -1e3bec26f5e89d9bad319c2fda261bcd9461680fb136162515a6e5a23759dad8 +215e7999afe08d627e98ea6ce0091e0ba2e46b8bc5290519485d8c23be89e1c0
diff --git a/a/1.txt b/N2/1.txt index b79ba68..d6d196b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -4,39 +4,27 @@ On Wed, 2010-09-29 at 15:00 +0200, Jan Kara wrote: > > > On Tue, Sep 28, 2010 at 12:25:48AM +0200, Jan Kara wrote: > > > > [Added CCs for similar ecryptfs warning] > > > > On Thu 23-09-10 12:38:49, Andrew Morton wrote: -> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; i= -t did not=20 -> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does= - not have=20 -> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which intro= -duces the=20 +> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; it did not +> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does not have +> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which introduces the > > > > > > warning. > > > > > > [...] -> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transi= -d 22342=20 +> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transid 22342 > > > > > > /dev/mapper/vg_cesarbinspiro-lv_home > > > > > > SELinux: initialized (dev dm-3, type btrfs), uses xattr > > > > > > ------------[ cut here ]------------ > > > > > > WARNING: at fs/fs-writeback.c:87 inode_to_bdi+0x62/0x6d() > > > > > > Hardware name: Inspiron N4010 -> > > > > > Dirtiable inode bdi default !=3D sb bdi btrfs -> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb=20 -> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hd= -a_intel=20 -> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev = -snd_seq=20 -> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl3= -2 btusb=20 -> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi del= -l_laptop snd=20 -> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_= -page_alloc=20 -> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd= - aes_x86_64=20 -> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_= -helper drm=20 -> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wai= -t_scan] +> > > > > > Dirtiable inode bdi default != sb bdi btrfs +> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb +> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hda_intel +> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev snd_seq +> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl32 btusb +> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi dell_laptop snd +> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_page_alloc +> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd aes_x86_64 +> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_helper drm +> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan] > > > > > > Pid: 1073, comm: find Not tainted 2.6.36-rc5+ #8 > > > > > > Call Trace: > > > > > > [<ffffffff8104d0e4>] warn_slowpath_common+0x85/0x9d @@ -48,36 +36,27 @@ t_scan] > > > > > > [<ffffffff8112259b>] vfs_readdir+0x8d/0xb4 > > > > > > [<ffffffff8112270b>] sys_getdents+0x81/0xd1 > > > > > > [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b -> > > > Thanks for the report. These bdi pointers are a mess. As Chri= -s pointed -> > > > out, btrfs forgets to properly initialize inode->i_mapping.back= -ing_dev_info -> > > > for directories and special inodes and thus these were previous= -ly attached -> > > > to default_backing_dev_info which probably isn't what Chris wou= -ld like to +> > > > Thanks for the report. These bdi pointers are a mess. As Chris pointed +> > > > out, btrfs forgets to properly initialize inode->i_mapping.backing_dev_info +> > > > for directories and special inodes and thus these were previously attached +> > > > to default_backing_dev_info which probably isn't what Chris would like to > > > > see. -> > >=20 -> > > There's no actual writeback for these, so it works fine for btrfs= - either +> > > +> > > There's no actual writeback for these, so it works fine for btrfs either > > > way. -> >=20 -> > Side note: every time inode is marked as dirty, we wake up a bdi th= -read +> > +> > Side note: every time inode is marked as dirty, we wake up a bdi thread > > or the default bdi thread. So if we have inodes which do not need > > write-back, we should never mark them as dirty. -> Are you sure? I think we wake up the thread only when it's the firs= -t +> Are you sure? I think we wake up the thread only when it's the first > dirty inode for the bdi... Err, right. If no one ever marks it as clean then we won't wake-up the thread. But I thought that marking it as dirty even once is bad because this causes bdi thread creation, which consumes resources. -Sorry for my ignorance, I did not really follow the conversation, I jus= -t -remember that when I looked at bdi stuff, I noticed that during boot th= -e +Sorry for my ignorance, I did not really follow the conversation, I just +remember that when I looked at bdi stuff, I noticed that during boot the kernel created many bdi threads which were never used then. They eventually exited. But I thought that creating useless bdi threads it about concuming resources and slowing down the boot. @@ -87,13 +66,11 @@ As I remember, the reason was touch_atime() for some of the threads. But really, I did not dig this, I just noticed this conversation and wanted to let you know about the issue I noticed this summer. ---=20 +-- Best Regards, -Artem Bityutskiy (=D0=90=D1=80=D1=82=D1=91=D0=BC =D0=91=D0=B8=D1=82=D1=8E= -=D1=86=D0=BA=D0=B8=D0=B9) +Artem Bityutskiy (Артём Битюцкий) -- -To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = -in +To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index e6a5558..1758c07 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -30,39 +30,27 @@ "> > > On Tue, Sep 28, 2010 at 12:25:48AM +0200, Jan Kara wrote:\n" "> > > > [Added CCs for similar ecryptfs warning]\n" "> > > > On Thu 23-09-10 12:38:49, Andrew Morton wrote:\n" - "> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; i=\n" - "t did not=20\n" - "> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does=\n" - " not have=20\n" - "> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which intro=\n" - "duces the=20\n" + "> > > > > > This started appearing for me on v2.6.36-rc5-49-gc79bd89; it did not \n" + "> > > > > > happen on v2.6.36-rc5-33-g1ce1e41, probably because it does not have \n" + "> > > > > > commit 692ebd17c2905313fff3c504c249c6a0faad16ec which introduces the \n" "> > > > > > warning.\n" "> > > > > > [...]\n" - "> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transi=\n" - "d 22342=20\n" + "> > > > > > device fsid 44d595920ddedfa-3ece6b56e80f689e devid 1 transid 22342 \n" "> > > > > > /dev/mapper/vg_cesarbinspiro-lv_home\n" "> > > > > > SELinux: initialized (dev dm-3, type btrfs), uses xattr\n" "> > > > > > ------------[ cut here ]------------\n" "> > > > > > WARNING: at fs/fs-writeback.c:87 inode_to_bdi+0x62/0x6d()\n" "> > > > > > Hardware name: Inspiron N4010\n" - "> > > > > > Dirtiable inode bdi default !=3D sb bdi btrfs\n" - "> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb=20\n" - "> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hd=\n" - "a_intel=20\n" - "> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev =\n" - "snd_seq=20\n" - "> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl3=\n" - "2 btusb=20\n" - "> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi del=\n" - "l_laptop snd=20\n" - "> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_=\n" - "page_alloc=20\n" - "> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd=\n" - " aes_x86_64=20\n" - "> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_=\n" - "helper drm=20\n" - "> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wai=\n" - "t_scan]\n" + "> > > > > > Dirtiable inode bdi default != sb bdi btrfs\n" + "> > > > > > Modules linked in: ipv6 kvm_intel kvm uinput arc4 ecb \n" + "> > > > > > snd_hda_codec_intelhdmi snd_hda_codec_realtek iwlagn snd_hda_intel \n" + "> > > > > > iwlcore snd_hda_codec uvcvideo snd_hwdep mac80211 videodev snd_seq \n" + "> > > > > > snd_seq_device v4l1_compat snd_pcm atl1c v4l2_compat_ioctl32 btusb \n" + "> > > > > > cfg80211 snd_timer i2c_i801 bluetooth iTCO_wdt dell_wmi dell_laptop snd \n" + "> > > > > > pcspkr wmi dcdbas shpchp iTCO_vendor_support soundcore snd_page_alloc \n" + "> > > > > > rfkill joydev microcode btrfs zlib_deflate libcrc32c cryptd aes_x86_64 \n" + "> > > > > > aes_generic xts gf128mul dm_crypt usb_storage i915 drm_kms_helper drm \n" + "> > > > > > i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan]\n" "> > > > > > Pid: 1073, comm: find Not tainted 2.6.36-rc5+ #8\n" "> > > > > > Call Trace:\n" "> > > > > > [<ffffffff8104d0e4>] warn_slowpath_common+0x85/0x9d\n" @@ -74,36 +62,27 @@ "> > > > > > [<ffffffff8112259b>] vfs_readdir+0x8d/0xb4\n" "> > > > > > [<ffffffff8112270b>] sys_getdents+0x81/0xd1\n" "> > > > > > [<ffffffff81009c72>] system_call_fastpath+0x16/0x1b\n" - "> > > > Thanks for the report. These bdi pointers are a mess. As Chri=\n" - "s pointed\n" - "> > > > out, btrfs forgets to properly initialize inode->i_mapping.back=\n" - "ing_dev_info\n" - "> > > > for directories and special inodes and thus these were previous=\n" - "ly attached\n" - "> > > > to default_backing_dev_info which probably isn't what Chris wou=\n" - "ld like to\n" + "> > > > Thanks for the report. These bdi pointers are a mess. As Chris pointed\n" + "> > > > out, btrfs forgets to properly initialize inode->i_mapping.backing_dev_info\n" + "> > > > for directories and special inodes and thus these were previously attached\n" + "> > > > to default_backing_dev_info which probably isn't what Chris would like to\n" "> > > > see.\n" - "> > >=20\n" - "> > > There's no actual writeback for these, so it works fine for btrfs=\n" - " either\n" + "> > > \n" + "> > > There's no actual writeback for these, so it works fine for btrfs either\n" "> > > way.\n" - "> >=20\n" - "> > Side note: every time inode is marked as dirty, we wake up a bdi th=\n" - "read\n" + "> > \n" + "> > Side note: every time inode is marked as dirty, we wake up a bdi thread\n" "> > or the default bdi thread. So if we have inodes which do not need\n" "> > write-back, we should never mark them as dirty.\n" - "> Are you sure? I think we wake up the thread only when it's the firs=\n" - "t\n" + "> Are you sure? I think we wake up the thread only when it's the first\n" "> dirty inode for the bdi...\n" "\n" "Err, right. If no one ever marks it as clean then we won't wake-up the\n" "thread. But I thought that marking it as dirty even once is bad because\n" "this causes bdi thread creation, which consumes resources.\n" "\n" - "Sorry for my ignorance, I did not really follow the conversation, I jus=\n" - "t\n" - "remember that when I looked at bdi stuff, I noticed that during boot th=\n" - "e\n" + "Sorry for my ignorance, I did not really follow the conversation, I just\n" + "remember that when I looked at bdi stuff, I noticed that during boot the\n" "kernel created many bdi threads which were never used then. They\n" "eventually exited. But I thought that creating useless bdi threads it\n" "about concuming resources and slowing down the boot.\n" @@ -113,15 +92,13 @@ "But really, I did not dig this, I just noticed this conversation and\n" "wanted to let you know about the issue I noticed this summer.\n" "\n" - "--=20\n" + "-- \n" "Best Regards,\n" - "Artem Bityutskiy (=D0=90=D1=80=D1=82=D1=91=D0=BC =D0=91=D0=B8=D1=82=D1=8E=\n" - "=D1=86=D0=BA=D0=B8=D0=B9)\n" + "Artem Bityutskiy (\320\220\321\200\321\202\321\221\320\274 \320\221\320\270\321\202\321\216\321\206\320\272\320\270\320\271)\n" "\n" "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-btrfs\" =\n" - "in\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-btrfs\" in\n" "the body of a message to majordomo@vger.kernel.org\n" More majordomo info at http://vger.kernel.org/majordomo-info.html -1e3bec26f5e89d9bad319c2fda261bcd9461680fb136162515a6e5a23759dad8 +22979087d423ea9d5d1094397357165b3206a7e16822d7aff96908cc41d5fa22
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.