From: Jan Kara <jack@suse.cz> To: Amir Goldstein <amir73il@gmail.com> Cc: Jan Kara <jack@suse.cz>, Linux Audit <linux-audit@redhat.com>, Paul Moore <paul@paul-moore.com>, linux-fsdevel <linux-fsdevel@vger.kernel.org>, Al Viro <viro@zeniv.linux.org.uk>, Richard Guy Briggs <rgb@redhat.com> Subject: Re: [PATCH 5/6] audit: Make hash table insertion safe against concurrent lookups Date: Tue, 3 Jul 2018 17:31:09 +0200 [thread overview] Message-ID: <20180703153109.2krilssfevbva57x@quack2.suse.cz> (raw) In-Reply-To: <CAOQ4uxivvqHD-xZDmWDT56g0xs2y9p5t7UC8y+RbTNXWfBu66g@mail.gmail.com> On Fri 29-06-18 16:02:10, Amir Goldstein wrote: > On Thu, Jun 28, 2018 at 7:40 PM, Jan Kara <jack@suse.cz> wrote: > > Currently, the audit tree code does not make sure that when a chunk in > > inserted into the hash table, it is fully initialized. So in theory (in > > practice only on DEC Alpha) a user of RCU lookup could see uninitialized > > structure in the hash table and crash. Add appropriate barriers between > > initialization of the structure and its insertion into hash table. > > > > Signed-off-by: Jan Kara <jack@suse.cz> ... > > @@ -466,6 +481,13 @@ static int tag_chunk(struct inode *inode, struct audit_tree *tree) > > tree->root = chunk; > > list_add(&tree->same_root, &chunk->trees); > > } > > + /* > > + * Make sure chunk is fully initialized before making it visible in the > > + * hash. Pairs with a data dependency barrier in READ_ONCE() in > > + * audit_tree_lookup(). > > + */ > > + smp_wmb(); > > + list_replace_rcu(&old->hash, &chunk->hash); > > IMO, now that list_replace_rcu() is no longer a one liner (including the wmb and > comment above) it would be cleaner to have a helper update_hash(old, chunk) > right next to insert_hash() and for the same reason smp_wmb with the comment > should go into insert_hash() helpler. I was thinking about this as well when writing the code. What I disliked about hiding smp_wmb() in some helper function is that after that it's much less obvious that you should have a good reason to add anything after smp_wmb() as RCU readers needn't see your write. However with some commenting, I guess it should be obvious enough. I'll do that as a separate cleanup patch though. Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz> To: Amir Goldstein <amir73il@gmail.com> Cc: Jan Kara <jack@suse.cz>, Richard Guy Briggs <rgb@redhat.com>, Linux Audit <linux-audit@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>, linux-fsdevel <linux-fsdevel@vger.kernel.org> Subject: Re: [PATCH 5/6] audit: Make hash table insertion safe against concurrent lookups Date: Tue, 3 Jul 2018 17:31:09 +0200 [thread overview] Message-ID: <20180703153109.2krilssfevbva57x@quack2.suse.cz> (raw) In-Reply-To: <CAOQ4uxivvqHD-xZDmWDT56g0xs2y9p5t7UC8y+RbTNXWfBu66g@mail.gmail.com> On Fri 29-06-18 16:02:10, Amir Goldstein wrote: > On Thu, Jun 28, 2018 at 7:40 PM, Jan Kara <jack@suse.cz> wrote: > > Currently, the audit tree code does not make sure that when a chunk in > > inserted into the hash table, it is fully initialized. So in theory (in > > practice only on DEC Alpha) a user of RCU lookup could see uninitialized > > structure in the hash table and crash. Add appropriate barriers between > > initialization of the structure and its insertion into hash table. > > > > Signed-off-by: Jan Kara <jack@suse.cz> ... > > @@ -466,6 +481,13 @@ static int tag_chunk(struct inode *inode, struct audit_tree *tree) > > tree->root = chunk; > > list_add(&tree->same_root, &chunk->trees); > > } > > + /* > > + * Make sure chunk is fully initialized before making it visible in the > > + * hash. Pairs with a data dependency barrier in READ_ONCE() in > > + * audit_tree_lookup(). > > + */ > > + smp_wmb(); > > + list_replace_rcu(&old->hash, &chunk->hash); > > IMO, now that list_replace_rcu() is no longer a one liner (including the wmb and > comment above) it would be cleaner to have a helper update_hash(old, chunk) > right next to insert_hash() and for the same reason smp_wmb with the comment > should go into insert_hash() helpler. I was thinking about this as well when writing the code. What I disliked about hiding smp_wmb() in some helper function is that after that it's much less obvious that you should have a good reason to add anything after smp_wmb() as RCU readers needn't see your write. However with some commenting, I guess it should be obvious enough. I'll do that as a separate cleanup patch though. Honza -- Jan Kara <jack@suse.com> SUSE Labs, CR
next prev parent reply other threads:[~2018-07-03 15:31 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-28 16:40 [PATCH 0/6] audit: Fix various races when tagging and untagging mounts Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-28 16:40 ` [PATCH 1/6] audit_tree: Replace mark->lock locking Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-29 11:31 ` Amir Goldstein 2018-06-29 11:31 ` Amir Goldstein 2018-07-03 14:07 ` Jan Kara 2018-07-03 14:07 ` Jan Kara 2018-06-28 16:40 ` [PATCH 2/6] audit: Fix possible spurious -ENOSPC error Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-29 11:42 ` Amir Goldstein 2018-06-29 11:42 ` Amir Goldstein 2018-07-02 6:05 ` Dan Carpenter 2018-07-02 6:05 ` Dan Carpenter 2018-07-03 14:18 ` Jan Kara 2018-07-03 14:18 ` Jan Kara 2018-06-28 16:40 ` [PATCH 3/6] audit: Fix possible tagging failures Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-29 12:05 ` Amir Goldstein 2018-06-29 12:05 ` Amir Goldstein 2018-07-03 14:21 ` Jan Kara 2018-07-03 14:21 ` Jan Kara 2018-07-03 17:42 ` Amir Goldstein 2018-07-03 17:42 ` Amir Goldstein 2018-07-04 8:28 ` Jan Kara 2018-07-04 8:28 ` Jan Kara 2018-06-28 16:40 ` [PATCH 4/6] audit: Embed key into chunk Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-29 12:53 ` Amir Goldstein 2018-06-29 12:53 ` Amir Goldstein 2018-07-03 14:25 ` Jan Kara 2018-07-03 14:25 ` Jan Kara 2018-06-28 16:40 ` [PATCH 5/6] audit: Make hash table insertion safe against concurrent lookups Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-29 13:02 ` Amir Goldstein 2018-06-29 13:02 ` Amir Goldstein 2018-07-03 15:31 ` Jan Kara [this message] 2018-07-03 15:31 ` Jan Kara 2018-06-28 16:40 ` [PATCH 6/6] audit: Point to fsnotify mark instead of embedding it Jan Kara 2018-06-28 16:40 ` Jan Kara 2018-06-29 13:20 ` Amir Goldstein 2018-06-29 13:20 ` Amir Goldstein 2018-07-04 12:34 ` Jan Kara 2018-07-04 12:34 ` Jan Kara 2018-06-29 11:44 ` [PATCH 0/6] audit: Fix various races when tagging and untagging mounts Amir Goldstein 2018-06-29 11:44 ` Amir Goldstein 2018-06-29 18:01 ` Paul Moore 2018-06-29 18:01 ` Paul Moore 2018-07-03 14:14 ` Jan Kara 2018-07-03 14:14 ` Jan Kara 2018-07-03 17:03 ` Paul Moore 2018-07-03 17:03 ` Paul Moore
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=20180703153109.2krilssfevbva57x@quack2.suse.cz \ --to=jack@suse.cz \ --cc=amir73il@gmail.com \ --cc=linux-audit@redhat.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=paul@paul-moore.com \ --cc=rgb@redhat.com \ --cc=viro@zeniv.linux.org.uk \ /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: linkBe 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.