public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	Song Liu <song@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Guoqing Jiang <guoqing.jiang@linux.dev>,
	Stephen Bates <sbates@raithlin.com>,
	Martin Oliveira <Martin.Oliveira@eideticom.com>,
	David Sloan <David.Sloan@eideticom.com>,
	Logan Gunthorpe <logang@deltatee.com>
Subject: [PATCH v2 0/3] A couple more bug fixes
Date: Thu,  8 Sep 2022 10:15:13 -0600	[thread overview]
Message-ID: <20220908161516.4361-1-logang@deltatee.com> (raw)

Hey,

The first two patches are a resend of the two sent earlier with tags
collected and a couple minor typos fixed.

The third patch fixes the deadlock issue I brought up in another email.

These patches are based on the current md/md-next branch (526bd69b9d3).

Thanks,

Logan

--

David Sloan (1):
  md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk()

Logan Gunthorpe (2):
  md: Remove extra mddev_get() in md_seq_start()
  md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d

 drivers/md/md.c    | 1 -
 drivers/md/raid5.c | 5 ++++-
 2 files changed, 4 insertions(+), 2 deletions(-)


base-commit: 526bd69b9d330eed1db59b2cf6a7d18caf866847
--
2.30.2

             reply	other threads:[~2022-09-08 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 16:15 Logan Gunthorpe [this message]
2022-09-08 16:15 ` [PATCH v2 1/3] md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() Logan Gunthorpe
2022-09-08 16:15 ` [PATCH v2 2/3] md: Remove extra mddev_get() in md_seq_start() Logan Gunthorpe
2022-09-09  4:53   ` Paul Menzel
2022-09-08 16:15 ` [PATCH v2 3/3] md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d Logan Gunthorpe
2022-09-15 15:15   ` Logan Gunthorpe
2022-09-19 18:31     ` Song Liu
2022-09-09 14:41 ` [PATCH v2 0/3] A couple more bug fixes Song Liu

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=20220908161516.4361-1-logang@deltatee.com \
    --to=logang@deltatee.com \
    --cc=David.Sloan@eideticom.com \
    --cc=Martin.Oliveira@eideticom.com \
    --cc=guoqing.jiang@linux.dev \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=sbates@raithlin.com \
    --cc=song@kernel.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