On Mon, Aug 11, 2008 at 07:39:15PM +1000, Mark Goodwin wrote:
> 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 that will enter into file-system? The
>>>> problem with trace buffers is telling us to clean this code path.
>>>>
>>>> By the way, I browse the source code from lxr.linux.no.
>>>> If I have to browse the latest xfs source code with linux
>>>> kernel that is used at SGI, how can I do that?
>>>>
>>> Any pointers on this? I wish to setup my own xfs development enviroment
>>> and details on this will be helpful.
>>
>> Well, you could look at the XFS home page and follow the links to:
>
> where? Did this URL get edited out (as seems to be happening lately)
> or did you neglect to paste it in?
Nope, the url got removed. it pointed to (using the same trick as last
time):
oss.sgi.com/projects/xfs/source.html
>> 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
Note that this one didn't, but barracuda thought it was a http
URI and gave a nasty warning about it:
| X-Barracuda-Spam-Status: No, SCORE=-0.49 using per-user scores of
TAG_LEVEL=2.0
| QUARANTINE_LEVEL=1000.0 KILL_LEVEL=2.1 tests=WEIRD_PORT
| X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.1.2330
| Rule breakdown below
| pts rule name description
| ---- ----------------------
--------------------------------------------------
| 1.50 WEIRD_PORT URI: Uses non-standard port number for
HTTP
Given that I can send URLs to myself, to lkml, friends, etc
and they work, this points to something specific to the XFS mailing
list....
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
|