From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Mark Harmstone <mark@harmstone.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pali@kernel.org" <pali@kernel.org>,
"dsterba@suse.cz" <dsterba@suse.cz>,
"aaptel@suse.com" <aaptel@suse.com>,
"willy@infradead.org" <willy@infradead.org>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"joe@perches.com" <joe@perches.com>,
"nborisov@suse.com" <nborisov@suse.com>
Subject: RE: [PATCH v5 02/10] fs/ntfs3: Add initialization of super block
Date: Fri, 18 Sep 2020 16:43:08 +0000 [thread overview]
Message-ID: <57419fb6b3764ed3bc7b0c3d284e9407@paragon-software.com> (raw)
In-Reply-To: <2011cd8c-7dc4-b2e7-114b-d5647336ec92@harmstone.com>
From: Mark Harmstone <mark.harmstone@gmail.com> On Behalf Of Mark Harmstone
Sent: Friday, September 11, 2020 7:50 PM
> Subject: Re: [PATCH v5 02/10] fs/ntfs3: Add initialization of super block
>
> Also, I think it would be a good idea if you *are* going to have static SDs, to
> allocate them dynamically rather than using a blob. The blobs' contents don't
> match your comments,
Hi Mark! Fixed the comment thing. Check out the V6.
V6 also introduces the system.ntfs_security xattr.
>and it'd have been picked up if you'd done that!
>
> s_dir_security translates to:
> owner S-1-5-32-544 (Administrators)
> group S-1-5-32-544 (Administrators)
> ACE: allow S-1-1-0 (Everyone) with FILE_ALL_ACCESS
>
> s_file_security translates to:
> owner S-1-1-0 (Everyone)
> group S-1-5-21-1987932187-4155540637-3944497785-513 (your personal SID?!)
> ACE: allow S-1-1-0 (Everyone) with FILE_ALL_ACCESS
>
>
> On 11/9/20 3:10 pm, Konstantin Komarov wrote:
> > This adds initialization of super block
> >
[]
> > +}
> > +
> > +MODULE_LICENSE("GPL");
> > +MODULE_DESCRIPTION("ntfs3 filesystem");
> > +MODULE_AUTHOR("Konstantin Komarov");
> > +MODULE_ALIAS_FS("ntfs3");
> > +
> > +module_init(init_ntfs_fs) module_exit(exit_ntfs_fs)
>
Thanks
prev parent reply other threads:[~2020-09-18 16:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 14:10 [PATCH v5 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2020-09-12 2:28 ` Joe Perches
2020-09-11 14:10 ` [PATCH v5 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2020-09-13 18:43 ` Joe Perches
2020-09-14 2:38 ` Matthew Wilcox
2020-09-18 16:35 ` Konstantin Komarov
2020-09-18 16:54 ` Matthew Wilcox
2020-09-25 16:04 ` Konstantin Komarov
2020-09-18 16:29 ` Konstantin Komarov
2020-09-18 16:38 ` Matthew Wilcox
2020-09-11 14:10 ` [PATCH v5 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 06/10] fs/ntfs3: Add compression Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2020-09-21 13:26 ` Pali Rohár
2020-09-25 16:30 ` Konstantin Komarov
2020-09-26 8:23 ` Pali Rohár
2020-10-09 15:31 ` Konstantin Komarov
2020-10-09 15:47 ` Pali Rohár
2020-09-11 14:10 ` [PATCH v5 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2020-09-11 14:10 ` [PATCH v5 10/10] fs/ntfs3: Add MAINTAINERS Konstantin Komarov
[not found] ` <20200911141018.2457639-3-almaz.alexandrovich@paragon-software.com>
[not found] ` <c819ee72-6bb0-416d-dfc4-0bc2ad6d0ccd@harmstone.com>
2020-09-18 16:39 ` [PATCH v5 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
[not found] ` <2011cd8c-7dc4-b2e7-114b-d5647336ec92@harmstone.com>
2020-09-18 16:43 ` Konstantin Komarov [this message]
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=57419fb6b3764ed3bc7b0c3d284e9407@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=aaptel@suse.com \
--cc=dsterba@suse.cz \
--cc=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@harmstone.com \
--cc=nborisov@suse.com \
--cc=pali@kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).