From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Overwriting copy functionality in filesystem
Date: Sat, 23 Mar 2019 15:01:56 -0400 [thread overview]
Message-ID: <13539.1553367716@turing-police> (raw)
In-Reply-To: <20190323165945.GA13199@bharath12345-Inspiron-5559>
On Sat, 23 Mar 2019 22:29:45 +0530, Bharath Vedartham said:
> I was wondering how we can overwrite the copy functionality while
> writing our own filesystem in linux.
> VFS does not offer any sort of API for copy. I think it calls create and
> write when we execute the copy the file/dir.
Which you can verify using strace. Which you should already be familiar with
if you have the experience needed to write a usable filesystem.
> I am interested in overwriting the way copy happens in my
> filesystem(which I am writing for fun :p).
And what, exactly, do you want copy to do differently on the API level,
and on the file system level?
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-03-23 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 16:59 Overwriting copy functionality in filesystem Bharath Vedartham
2019-03-23 19:01 ` Valdis Klētnieks [this message]
2019-03-24 13:18 ` Bharath Vedartham
2019-03-24 14:06 ` Valdis Klētnieks
2019-03-28 18:30 ` Bharath Vedartham
2019-03-28 20:07 ` Valdis Klētnieks
2019-03-23 19:03 ` Bernd Petrovitsch
2019-03-24 13:21 ` Bharath Vedartham
2019-03-23 19:05 ` Greg KH
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=13539.1553367716@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux.bhar@gmail.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.