Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add mknod support #158

Merged
merged 1 commit into from
May 23, 2019
Merged

add mknod support #158

merged 1 commit into from
May 23, 2019

Conversation

KnightKu
Copy link
Contributor

Add new option '-k' to support file creation test with mknod,
which is widely used in lustre.

Signed-off-by: Gu Zheng gzheng@ddn.com

Add new option '-k' to support file creation test with mknod,
which is widely used in lustre.

Signed-off-by: Gu Zheng <gzheng@ddn.com>
Copy link
Collaborator

@JulianKunkel JulianKunkel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing. Could you add something to the documentation and add that as subsequent pull request?

{
int *fd;

fd = (int *)malloc(sizeof(int));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not optimal, as with Mknod you do not call POSIX_close() which calls free(fd). I will fix this, though in a subsequent patch.

@JulianKunkel JulianKunkel merged commit 942aa95 into hpc:master May 23, 2019
@JulianKunkel
Copy link
Collaborator

Now that I did some further testing, as you create regular files at the moment, these could support "-w" and File_close(). Or do you aim to use it to create special inodes and such?

@KnightKu
Copy link
Contributor Author

Hi @JulianKunkel , thanks for your quick review and improvement.
We only use it to create regular files at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants