Use KM_NOFS for debug trace buffers Use KM_NOFS to prevent recursion back into the filesystem which can cause deadlocks. In the case of xfs_iread() we hold the lock on the inode cluster buffer while
I couldn't get a chance to read the diff's completely. If I click on Lachlan's url for diff's, I couldn't access them. It looks to me that the issue is not just with trace buffers. It can extend to x
Ok, something is stripping URLs out of emails. I just sent that URL to myself and it wasn't stripped so it's not my mail infrastructure that is doing it. Did someone "upgrade" the spam filters on oss
Dave Chinner wrote: On Thu, Aug 07, 2008 at 06:27:46AM +1000, Dave Chinner wrote: On Thu, Aug 07, 2008 at 06:19:57AM +1000, Dave Chinner wrote: On Wed, Aug 06, 2008 at 10:42:15PM +0530, Bhagi rathi w
Thanks Dave. However, My concern is just not one allocation. We need to clean all allocations that can re-enter to file-system. I see that this issue exists in attributes format for i_afp allocations
Sorry for the later review, but the xfs_super.c changes don't make sense. These allocations are done during module_init time and thus it'ss fien to call back into any fs to reclaim pages for it. Fort
Is the above issue fixed already? I see this existing in latest linux kernel. Any pointers on this? I wish to setup my own xfs development enviroment and details on this will be helpful. Cheers, Bhag
Well, you could look at the XFS home page and follow the links to: Or for just the kernel source you can use the master branch of the XFS git tree at: git://oss.sgi.com:8090/xfs/xfs-2.6.git master Ch
We maintain a CVS tree of xfs-dev on oss. It's slightly different to mainline linux as it contains patches to include kdb and dmapi. From the web page: Set the CVSROOT environment variable. $ export
Reply in verbatim below ... Dave Chinner wrote: On Fri, Aug 08, 2008 at 10:46:56AM +0530, Bhagi rathi wrote: Are we safe that we fixed all these real problems by looking into possible allocations tha
Nope, the url got removed. it pointed to (using the same trick as last time): oss.sgi.com/projects/xfs/source.html Note that this one didn't, but barracuda thought it was a http URI and gave a nasty
Use KM_NOFS for debug trace buffers Use KM_NOFS to prevent recursion back into the filesystem which can cause deadlocks. In the case of xfs_iread() we hold the lock on the inode cluster buffer while
I couldn't get a chance to read the diff's completely. If I click on Lachlan's url for diff's, I couldn't access them. It looks to me that the issue is not just with trace buffers. It can extend to x