All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Seunguk Shin <seunguk.shin@samsung.com>,
	"'Martin K. Petersen'" <martin.petersen@oracle.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org, g.danti@assyoma.it
Subject: Re: [PATCH] raid0: data corruption when using trim
Date: Fri, 24 Jul 2015 08:47:44 +0200	[thread overview]
Message-ID: <55B1DF90.7090904@assyoma.it> (raw)
In-Reply-To: <005601d0c470$951ea860$bf5bf920$@samsung.com>

> Martine,
>
> I have tested the script from Algolia with your patch, I cannot see the same
> symptoms I saw with original kernel. I think the patch works and there is no
> problem.
>
> Thank you,
> Seunguk Shin
>

Hi, any idea on why the bug affects/manifests only on specific SATA 
SSDs? It is timing related, or it depends on how the controller manage 
TRIM requests?

Thanks.

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  parent reply	other threads:[~2015-07-24  6:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19  3:28 [PATCH] raid0: data corruption when using trim Seunguk Shin
2015-07-20 12:33 ` Martin K. Petersen
2015-07-20 17:38   ` Piergiorgio Sartor
2015-07-20 18:26     ` Martin K. Petersen
2015-07-20 18:34       ` Piergiorgio Sartor
2015-07-21  4:28         ` Martin K. Petersen
2015-07-23 16:46           ` Gionatan Danti
2015-07-23 22:17             ` Martin K. Petersen
2015-07-24  6:37               ` Gionatan Danti
2015-07-21  4:18   ` Seunguk Shin
2015-07-21  4:55     ` Martin K. Petersen
2015-07-22 11:21       ` Seunguk Shin
2015-07-22 11:59         ` Martin K. Petersen
2015-07-24  6:47         ` Gionatan Danti [this message]
     [not found]           ` <023401d0c60a$fff39330$ffdab990$@samsung.com>
2015-07-24 14:42             ` Gionatan Danti
2015-07-24 15:03           ` Martin K. Petersen

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=55B1DF90.7090904@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=neilb@suse.de \
    --cc=seunguk.shin@samsung.com \
    /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.