From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: "linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Vladimir Koushnir
<vladimirk-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Jim Mott <jim-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH v2 opensm] Add support for synchronizing in memory files with storage
Date: Sat, 21 Dec 2013 11:33:42 -0500 [thread overview]
Message-ID: <52B5C2E6.9050905@dev.mellanox.co.il> (raw)
In-Reply-To: <52B59E5D.4000207-HInyCGIudOg@public.gmane.org>
On 12/21/2013 8:57 AM, Bart Van Assche wrote:
> On 12/21/13 13:54, Hal Rosenstock wrote:
>> -int osm_db_store(IN osm_db_domain_t * p_domain)
>> +int osm_db_store(IN osm_db_domain_t * p_domain,
>> + IN boolean_t fsync_high_avail_files)
>
> Version two of this patch looks fine to me, but while reviewing this
> patch I noticed two issues in osm_db_store() that might need to be
> addressed:
> * With p_domain_imp->dirty == FALSE cl_spinlock_release() is called
> without having invoked cl_spinlock_acquire() first. Can the 'dirty' flag
> be modified concurrently with the test of the 'dirty' flag ? If so, the
> test of this flag probably has to occur after the spinlock has been
> acquired.
Yes; I'll fix this in a subsequent patch.
> * If the malloc() call for allocating the temporary file name fails then
> strcpy() will be called with NULL as first argument. Shouldn't the
> return value of malloc() be checked ?
Ditto.
Thanks.
-- Hal
> Thanks,
>
> Bart.
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-12-21 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 12:54 [PATCH v2 opensm] Add support for synchronizing in memory files with storage Hal Rosenstock
[not found] ` <52B58F98.7040804-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2013-12-21 13:57 ` Bart Van Assche
[not found] ` <52B59E5D.4000207-HInyCGIudOg@public.gmane.org>
2013-12-21 16:33 ` Hal Rosenstock [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=52B5C2E6.9050905@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=bvanassche-HInyCGIudOg@public.gmane.org \
--cc=jim-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vladimirk-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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.