From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: martin.petersen@oracle.com
Cc: Kernel Team <kernel-team@lists.ubuntu.com>,
linux-kernel@vger.kernel.org, snitzer@redhat.com,
jgarzik@redhat.com, JBottomley@Parallels.com
Subject: [v3.7 Regression] [SCSI] sd: Implement support for WRITE SAME
Date: Fri, 14 Dec 2012 15:30:44 -0500 [thread overview]
Message-ID: <50CB8C74.3090102@canonical.com> (raw)
Hi Martin,
A bug was opened against the Ubuntu kernel[0]. After a kernel bisect,
it was found that reverting the following commit resolved this bug:
commit 5db44863b6ebbb400c5e61d56ebe8f21ef48b1bd
Author: Martin K. Petersen <martin.petersen@oracle.com>
Date: Tue Sep 18 12:19:32 2012 -0400
[SCSI] sd: Implement support for WRITE SAME
The regression was introduced as of v3.7-rc7.
The bug can be reproduced with the following commands, which will
operate on a virtual scsi_debug device, so they won't change any data on
the test system. However, this will completely crash the system:
sudo modprobe scsi_debug
sudo luksformat -t ext4 /dev/sdb <- Or whatever device gets assigned
after inserting scsi_debug.
sudo cryptsetup luksOpen /dev/sdb treasure
Everything works fine up to here, but the following will cause the crash:
sudo mount /dev/mapper/treasure /mnt
The bug can be reproduced on bare metal, in a VM and on i386 or amd64.
I see that you are the author of this patch, so I wanted to run this by
you. I was thinking of requesting a revert for v3.7, but I wanted to
get your feedback first.
Thanks,
Joe
[0] https://bugs.launchpad.net/bugs/1089818
next reply other threads:[~2012-12-14 20:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 20:30 Joseph Salisbury [this message]
2012-12-14 21:11 ` [v3.7 Regression] [SCSI] sd: Implement support for WRITE SAME Mike Snitzer
2012-12-15 2:38 ` Joseph Salisbury
2012-12-14 22:35 ` Martin K. Petersen
2012-12-15 2:40 ` Joseph Salisbury
2012-12-18 19:52 ` Joseph Salisbury
2012-12-19 16:58 ` Martin K. Petersen
2012-12-19 19:58 ` Mike Snitzer
2012-12-19 19:59 ` Joseph Salisbury
2012-12-19 20:45 ` Martin K. Petersen
2012-12-19 20:45 ` Martin K. Petersen
2012-12-19 20:45 ` Milan Broz
2012-12-19 21:07 ` [PATCH] dm-crypt: never use write same (was Re: [v3.7 Regression] [SCSI] sd: Implement support for WRITE SAME) Milan Broz
2012-12-19 21:07 ` Joseph Salisbury
2012-12-19 22:20 ` Joseph Salisbury
2012-12-19 22:23 ` Milan Broz
2015-07-13 16:33 ` Joseph Salisbury
2015-07-13 16:59 ` Milan Broz
2015-07-13 17:01 ` Milan Broz
2015-07-13 18:01 ` Mike Snitzer
2012-12-20 0:11 ` [PATCH] " Martin K. Petersen
2012-12-20 5:47 ` Mike Snitzer
2012-12-20 5:57 ` [PATCH 1/4] dm: default to disabling WRITE SAME support for all targets Mike Snitzer
2012-12-20 5:57 ` [PATCH 2/4] dm: add WRITE SAME support Mike Snitzer
2012-12-20 5:57 ` [PATCH 3/4] dm linear: " Mike Snitzer
2012-12-20 5:57 ` [PATCH 4/4] dm stripe: " Mike Snitzer
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=50CB8C74.3090102@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=JBottomley@Parallels.com \
--cc=jgarzik@redhat.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=snitzer@redhat.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.