2008/10/17 Christoph Hellwig <hch@xxxxxxxxxxxxx>: > On Fri, Oct 17, 2008 at 04:43:07PM +0400, Alexander Beregalov wrote: >> It is SMP x86_64, rootfs is on XFS > > The message comes from code in XFS, but I really wonder where the atomic > context comes from. xfs_iget_core has a few changes in the tree pulled > into todays Linux-next, but it's still missing the recent updates > redoing this area completely. In some ways it looks like this process > has the the atomic context flag left pending somewhere, but that should > also trigger warnings on the VFS locks like i_mutex. > > Very misterious. > > IS there a specific workload you can reproduce this with? > Workload is not specific, many i/o commands trigger the message. dmesg|grep comm: [ 4.419605] Pid: 1396, comm: mkdir Not tainted 2.6.27-next-20081017 #2 [ 6.056443] Pid: 1782, comm: dhcpcd Not tainted 2.6.27-next-20081017 #2 [ 17.899905] Pid: 1791, comm: dhcpcd-run-hook Not tainted 2.6.27-next-20081017 #2 [ 3846.588549] Pid: 2005, comm: screen Not tainted 2.6.27-next-20081017 #2 [ 4416.242723] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 [ 4430.618037] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 [ 4431.641578] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 [ 4432.944265] Pid: 2023, comm: git Not tainted 2.6.27-next-20081017 #2 [ 4590.330706] Pid: 2026, comm: git-merge Not tainted 2.6.27-next-20081017 #2 [14882.802479] Pid: 2058, comm: git-merge Not tainted 2.6.27-next-20081017 #2 [16955.026436] Pid: 2091, comm: git-merge Not tainted 2.6.27-next-20081017 #2 [18466.645935] Pid: 2119, comm: git-merge Not tainted 2.6.27-next-20081017 #2 [19165.813049] Pid: 2150, comm: git-merge Not tainted 2.6.27-next-20081017 #2 -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
