From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] What's your opinion on the patch to fix bug 58 for kernel 2.6 porting?
Date: Thu Apr 29 12:34:24 2004 [thread overview]
Message-ID: <20040429173135.GC9043@ca-server1.us.oracle.com> (raw)
In-Reply-To: <37FBBA5F3A361C41AB7CE44558C3448E03B65E90@PDSMSX403.ccr.corp.intel.com>
Well, to be perfectly honest I don't think this is the right solution.
Instead of peppering the code with signal stuff, why not try to figure out
what the timing issue is (it seems that the umount thread should wait on
pending operations) and fix it that way?
--Mark
On Thu, Apr 29, 2004 at 10:10:56AM +0800, Zhang, Sonic wrote:
> Hi Mark,
>
> Do you have any opinion on the patch to fix bug 58 for kernel
> 2.6 porting?
> Could you add the patch into the source tree?
>
> Thank you.
>
>
> *********************************************
> Sonic Zhang
> Software Engineer
> Intel China Software Lab
> Tel: (086)021-52574545-1667
> iNet: 752-1667
> *********************************************
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next prev parent reply other threads:[~2004-04-29 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 21:11 [Ocfs2-devel] What's your opinion on the patch to fix bug 58 for kernel 2.6 porting? Zhang, Sonic
2004-04-29 12:34 ` Mark Fasheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 20:20 Zhang, Sonic
2004-04-30 11:57 ` Joel Becker
2004-05-04 1:08 Zhang, Sonic
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=20040429173135.GC9043@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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.