All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	Sagi Grimberg
	<sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	target-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: srp state in current mainline
Date: Sun, 15 Nov 2015 11:48:08 -0800	[thread overview]
Message-ID: <5648E178.9010106@sandisk.com> (raw)
In-Reply-To: <20151115180621.GA24488-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

On 11/15/15 10:06, Christoph Hellwig wrote:
> FYI, I sent a patch for the zero S/G length issue.  With this xfstests
> does fine for ext4 and btrfs.  With XFS I still run into corruption
> warnings for the slab use after free poison pattern.  I suspect that
> issue might be related to uniqueue XFS I/O patterns.  One thing that
> might be related is that XFS can submit bios backed by kmalloced memory.
>
> I've also tested XFS on various other storage devices on the same kernel
> and didn't see an issue like that just to be sure.

Thanks for submitting that patch.

Did I understand correctly that page-aligned I/O works fine but I/O that 
is not aligned on a page boundary not ? Have you already had the time to 
verify whether the "IB/srp: Convert to new registration API" patch is 
the patch that introduced this issue ?

BTW, another location where a buffer is used that is not aligned on a 
page boundary is the scsi_probe_and_add_lun() function. If a crash 
occurs while probing LUNs or lsscsi shows garbled data for SRP LUNs that 
might indicate a problem in the buffer mapping or registration code.

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

  parent reply	other threads:[~2015-11-15 19:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 17:15 srp state in current mainline Christoph Hellwig
     [not found] ` <20151110171509.GA27781-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-11-11 15:35   ` Bart Van Assche
2015-11-11 15:46     ` Christoph Hellwig
2015-11-11 16:03       ` Bart Van Assche
     [not found]         ` <564366E2.8000209-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-11-11 16:18           ` Christoph Hellwig
     [not found]             ` <20151111161845.GA31542-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-11-11 16:34               ` Sagi Grimberg
2015-11-11 21:07   ` Bart Van Assche
2015-11-12 17:59     ` Christoph Hellwig
2015-11-13  1:12       ` Bart Van Assche
     [not found]         ` <564538EE.3050805-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-11-13  6:48           ` Christoph Hellwig
2015-11-15 18:06 ` Christoph Hellwig
     [not found]   ` <20151115180621.GA24488-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-11-15 19:48     ` Bart Van Assche [this message]
     [not found]       ` <5648E178.9010106-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-11-16  8:38         ` Christoph Hellwig
2015-11-22 13:53 ` Christoph Hellwig
2015-11-22 14:32   ` Christoph Hellwig
2015-11-22 14:55     ` Sagi Grimberg
     [not found]       ` <5651D775.9090500-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2015-11-22 15:10         ` Christoph Hellwig
2015-11-22 15:26           ` Sagi Grimberg
2015-11-22 15:31             ` Christoph Hellwig
     [not found]               ` <20151122153106.GA26919-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2015-11-24  1:14                 ` Bart Van Assche
2015-11-25 19:34                   ` Bart Van Assche
     [not found]                     ` <56560D46.1070904-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-11-26  1:17                       ` Bart Van Assche

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=5648E178.9010106@sandisk.com \
    --to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=target-devel-u79uwXL29TY76Z2rM5mHXA@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.