From: Russell Cattelan <cattelan@thebarn.com>
To: Bhagi rathi <jahnu77@gmail.com>,
Lachlan McIlroy <lachlan@sgi.com>,
xfs@oss.sgi.com
Subject: Re: TAKE 981498 - Use KM_NOFS for debug trace buffers
Date: Wed, 06 Aug 2008 21:19:28 -0500 [thread overview]
Message-ID: <489A5BB0.9020900@thebarn.com> (raw)
In-Reply-To: <20080806210355.GS21635@disturbed>
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 wrote:
>>>
>>>> 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 xfs_iformat
>>>> as well. The same dead-lock can spring via
>>>>
>>>> xfs_iread -> xfs_iformat -> xfs_iformat_extents -> xfs_iext_add ->
>>>> xfs_iext_inline_to_direct -> which can do kmem_alloc with
>>>> KM_SLEEP flag.
>>>>
>>> Fixed already:
>>>
>>>
>>>
>> Hmmm. where did that url go? Try again:
>>
>
> 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.sgi.com or the
> barracuda overnight?
>
not oss
I'm seeing the correct url's BTW
> The link - minus the "http://" bit is:
>
> oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commit;h=8c6266658cb76e282c14cb92f8ba5a1c674f4928
>
> let's see if that gets stripped....
>
> Cheers,
>
> Dave.
>
next prev parent reply other threads:[~2008-08-07 2:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 6:15 TAKE 981498 - Use KM_NOFS for debug trace buffers Lachlan McIlroy
2008-08-06 17:12 ` Bhagi rathi
2008-08-06 19:56 ` Eric Sandeen
2008-08-06 20:19 ` Dave Chinner
2008-08-06 20:27 ` Dave Chinner
2008-08-06 21:03 ` Dave Chinner
2008-08-07 2:19 ` Russell Cattelan [this message]
2008-08-07 17:45 ` Bhagi rathi
2008-08-07 17:43 ` Bhagi rathi
2008-08-08 5:16 ` Bhagi rathi
2008-08-07 22:04 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=489A5BB0.9020900@thebarn.com \
--to=cattelan@thebarn.com \
--cc=jahnu77@gmail.com \
--cc=lachlan@sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox