All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashley Pittman <ashley@pittman.co.uk>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [lustre-discuss] more on lustre striping
Date: Fri, 10 Jun 2016 13:29:02 +0100	[thread overview]
Message-ID: <575AB28E.7090404@pittman.co.uk> (raw)
In-Reply-To: <9ebe9f4c-d5a2-4c93-4f00-49029850cbbe@iodoctors.com>

On 22/05/16 02:56, John Bauer wrote:
>
> Oleg
>
> I can intercept the fopen(), but that does me no good as I can't set 
> the O_LOV_DELAY_CREATE bit.  What I can not intercept is the open() 
> downstream of fopen().  If one examines the symbols in libc you will 
> see there are no unsatisfied externals relating to open, which means 
> there is nothing for the runtime linker to find concerning open's.  I 
> will have a look at the Lustre 1.8 source, but I seriously doubt that 
> the open beneath fopen() was intercepted with LD_PRELOAD.  I would 
> love to find a way to do that.  I could throw away a lot of code. 
> Thanks,  John
>

Could you not intercept fopen() and implement it with calls to open() 
and fdopen() yourself which would give you full control over what you're 
looking for here?

Ashley.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20160610/ac16a068/attachment.htm>

  parent reply	other threads:[~2016-06-10 12:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1ef5a267-334c-be0d-13f4-c0fab917d1bf@iodoctors.com>
2016-05-21  5:51 ` [lustre-devel] [lustre-discuss] more on lustre striping Dilger, Andreas
2016-05-21 20:01   ` John Bauer
2016-05-21 20:08     ` Drokin, Oleg
2016-05-21 20:25       ` John Bauer
2016-05-22  0:33         ` Drokin, Oleg
2016-05-22  1:56           ` John Bauer
2016-05-22  2:49             ` Drokin, Oleg
2016-06-10 12:29             ` Ashley Pittman [this message]
2016-06-10 15:28               ` John Bauer
2016-06-10 16:04               ` John Bauer
2016-06-17 18:28                 ` Dilger, Andreas
2016-06-23 21:50                 ` Oleg Drokin
2016-06-26 19:17                   ` John Bauer

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=575AB28E.7090404@pittman.co.uk \
    --to=ashley@pittman.co.uk \
    --cc=lustre-devel@lists.lustre.org \
    /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.