All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Tony Battersby <tonyb@cybernetics.com>,
	stable <stable@vger.kernel.org>,
	linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
	Chris Mason <clm@fb.com>, Christoph Hellwig <hch@lst.de>,
	"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] block: fix splitting segments on boundary masks
Date: Mon, 20 Jul 2020 15:08:22 +0200	[thread overview]
Message-ID: <20200720130822.GC494210@kroah.com> (raw)
In-Reply-To: <75d5014a-d991-24f8-494c-fdca95205adb@roeck-us.net>

On Thu, Jul 09, 2020 at 08:26:01AM -0700, Guenter Roeck wrote:
> On 7/9/20 7:35 AM, Tony Battersby wrote:
> > Although I was not originally involved in the development of these
> > patches, I recently came across them while looking over the source:
> > 
> > upstream commit 429120f3df2d ("block: fix splitting segments on boundary masks")
> >     Cc: stable@vger.kernel.org # v5.1+
> >     Fixes: dcebd755926b ("block: use bio_for_each_bvec() to compute multi-page bvec count")
> > 
> > upstream commit 4a2f704eb2d8 ("block: fix get_max_segment_size() overflow on 32bit arch")
> >     Fixes: 429120f3df2d ("block: fix splitting segments on boundary masks")
> > 
> > https://www.spinics.net/lists/linux-block/msg48605.html
> > https://www.spinics.net/lists/linux-block/msg48959.html
> > 
> > 
> > The first patch mentions fixing problems with filesystem corruption, so
> > it seems important, but it has never been included in any -stable
> > kernel.  Is there a specific reason these patches have been excluded
> > from -stable, or is it just a mistake?
> > 
> See here:
> 
> https://www.spinics.net/lists/stable/msg355009.html
> 
> Looks like it was queued but dropped because of the problem that
> was later fixed with the patch below. Maybe it is time to revisit
> and apply both patches now.

Ok, let me queue both up for 5.4.y now and see what happens :)

thanks,

greg k-h

      reply	other threads:[~2020-07-20 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 14:35 [PATCH] block: fix splitting segments on boundary masks Tony Battersby
2020-07-09 15:26 ` Guenter Roeck
2020-07-20 13:08   ` Greg KH [this message]

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=20200720130822.GC494210@kroah.com \
    --to=greg@kroah.com \
    --cc=axboe@kernel.dk \
    --cc=clm@fb.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=ming.lei@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.org \
    --cc=tonyb@cybernetics.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.