Linux-Block Archive mirror
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Saranya Muruganandam <saranyamohan@google.com>
Cc: "chaitanyak@nvidia.com" <chaitanyak@nvidia.com>,
	"hch@lst.de" <hch@lst.de>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH v2] block/035: test return EIO from BLKRRPART
Date: Fri, 12 Apr 2024 07:13:59 +0000	[thread overview]
Message-ID: <tdaviirkvzqzemugdc4ursq7zbaabgpl5vowd2nt4uviq6i6z7@2wrp4nrwp6lv> (raw)
In-Reply-To: <20240411234742.590340-1-saranyamohan@google.com>

On Apr 11, 2024 / 23:47, Saranya Muruganandam wrote:
> When we fail to reread the partition superblock from the disk, due to
> bad sector or bad disk etc, BLKRRPART should fail with EIO.
> Simulate failure for the entire block device and run
> "blockdev --rereadpt" and expect it to fail and return EIO instead of
> pass.
> 
> Link: https://lore.kernel.org/all/20240405014253.748627-1-saranyamohan@google.com/
> Signed-off-by: Saranya Muruganandam <saranyamohan@google.com>

I've applied it, thanks. Please note that I modified the test case number from
block/035 to block/036.

  reply	other threads:[~2024-04-12  7:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  1:56 [PATCH blktests] block/035: test return EIO from BLKRRPART Saranya Muruganandam
2024-04-05  6:52 ` Christoph Hellwig
2024-04-05  7:52 ` Chaitanya Kulkarni
2024-04-05  8:05   ` Chaitanya Kulkarni
2024-04-06  4:46   ` Saranya Muruganandam
2024-04-08  6:45     ` Shinichiro Kawasaki
2024-04-10  0:15       ` Saranya Muruganandam
2024-04-10  5:13         ` Shinichiro Kawasaki
2024-04-10 17:02           ` Saranya Muruganandam
2024-04-11  5:29             ` Shinichiro Kawasaki
2024-04-11 23:47               ` [PATCH v2] " Saranya Muruganandam
2024-04-12  7:13                 ` Shinichiro Kawasaki [this message]
2024-04-05 17:48 ` [PATCH blktests] " 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=tdaviirkvzqzemugdc4ursq7zbaabgpl5vowd2nt4uviq6i6z7@2wrp4nrwp6lv \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=saranyamohan@google.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).