linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	open-osd mailing-list <osd-dev@open-osd.org>
Cc: Dan Carpenter <error27@gmail.com>
Subject: [PATCH 0/4] libosd: Last updates for Linux 2.6.30-rc
Date: Sun, 19 Apr 2009 18:58:58 +0300	[thread overview]
Message-ID: <49EB4A42.9030502@panasas.com> (raw)

Hi dear James, list

I would like to push these 3 patches to support OSD2 revision 5 wire
format, for the Linux 2.6.30-rcx series. So to minimize the maintainability
headache of having two Kernel versions with two separate wire formats.
(Pretending to be OSD2)

I have finally fixed the OSC's osd-target code to support OSD2 up to
revision 5, and am able to push these changes to the Linux initiator.
(Users will need the new HEAD at osd-target git-tree:
  git://git.open-osd.org/osc-osd master)

Revision 5 is suppose to be the very last changes to OSD2 wire format,
and is in general frozen state that should only accept fixes to the wording
of the text, if any exist.

The very first patch is a BUG fix sent by Dan Carpenter found with "smatch",
followed by three patches to fix the wire format for support of revision 5.
Only the very last patch actually changes the wire format, the first two
only refactor the code in preparation of the actual change.

Here is the list of patches:

[PATCH 1/4] potential ERR_PTR dereference in osd_initiator.c

[PATCH 2/4] libosd: OSD2r05: Prepare for rev5 attribute list changes
[PATCH 3/4] libosd: OSD2r05: OSD_CRYPTO_KEYID_SIZE will grow 20 => 32 bytes
[PATCH 4/4] libosd: OSD2r05: on-the-wire changes for latest OSD2 draft.

Please see last patch for summery of what changed.

Thanks in advance
Boaz

             reply	other threads:[~2009-04-19 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 15:58 Boaz Harrosh [this message]
2009-04-19 16:07 ` [PATCH 1/4] libosd: potential ERR_PTR dereference in osd_initiator.c Boaz Harrosh
2009-04-19 16:19   ` Boaz Harrosh
2009-04-19 16:11 ` [PATCH 2/4] libosd: OSD2r05: Prepare for rev5 attribute list changes Boaz Harrosh
2009-04-19 16:13 ` [PATCH 3/4] libosd: OSD2r05: OSD_CRYPTO_KEYID_SIZE will grow 20 => 32 bytes Boaz Harrosh
2009-04-19 16:17 ` [PATCH 4/4] libosd: OSD2r05: on-the-wire changes for latest OSD2 revision 5 Boaz Harrosh

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=49EB4A42.9030502@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=error27@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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).