From: Artur Wojcik <artur.wojcik@intel.com>
To: Andre Noll <maan@systemlinux.org>, Neil Brown <neilb@suse.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>
Subject: Re: [patch 0/1][mdadm] Fix needed to enable RAID volumes on SAS devices (version 2).
Date: Mon, 30 Nov 2009 16:12:13 +0100 [thread overview]
Message-ID: <1259593933.3178.122.camel@awojcik-linux> (raw)
In-Reply-To: <20091113193545.GW21495@skl-net.de>
Neil/Andre,
I incorporated the suggestions Andre gave me and this resulted in the
second version of patch. However I decided to not use pathconf()
function but to define PATH_MAX instead. It is just the size of a buffer
and I would like this to be resolved during compilation time rather then
dynamically during execution time. Please review it and let me know if
something needs to be changed.
As for the being paranoid... so I really am, if we talk about software
security and vulnerability. I decided to introduce a new __str_fmt()
function and str_fmt() helper macro. Both are documented in source code
(let me know if you need separate patch for this).
-------------------------------------------------
This fix allows to create a RAID arrays on SAS devices direct-attached
or installed behind an expander. The cause of the problem is assumption
that 50 characters is enough to fit sysfs path of a storage device. This
is true for devices connected to AHCI and IDE controllers. However for
SAS devices (especially installed behind an expander) 'libsas' may
create a path much longer then 50 characters and in consequence the path
is truncated and incorrectly evaluated.
---
Detail.c | 5 ++-
platform-intel.c | 19 ++++++++-------
super-intel.c | 27 ++++++++-------------
sysfs.c | 59 ++++++++++++++++++++++-------------------------
util.c | 55 +++++++++++++++++++++++++++++++++++---------
util.h | 67
++++++++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 162 insertions(+), 70 deletions(-)
create mode 100644 util.h
---
Artur
next prev parent reply other threads:[~2009-11-30 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 10:43 [patch 1/1][mdadm] Fix needed to enable RAID device creation on SAS devices Wojcik, Artur
2009-11-13 19:35 ` Andre Noll
2009-11-30 15:12 ` Artur Wojcik [this message]
2009-12-08 5:37 ` [patch 0/1][mdadm] Fix needed to enable RAID volumes on SAS devices (version 2) Neil Brown
2009-12-09 17:41 ` Artur Wojcik
2009-12-09 18:12 ` Dan Williams
2009-11-30 15:12 ` [patch 1/1][mdadm] " Artur Wojcik
2009-11-30 19:56 ` Dan Williams
2009-12-01 11:52 ` Artur Wojcik
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=1259593933.3178.122.camel@awojcik-linux \
--to=artur.wojcik@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=maan@systemlinux.org \
--cc=neilb@suse.de \
/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).