stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Floppy ioctl range clamping fixes
Date: Fri, 19 Jul 2019 19:07:18 +0200	[thread overview]
Message-ID: <20190719170718.GA32664@kroah.com> (raw)
In-Reply-To: <CAHk-=wg+aNdzECivhrKrBr8CzEuMuhPg40DcH=jgmNSD+Ns_Fw@mail.gmail.com>

On Thu, Jul 18, 2019 at 09:29:06PM -0700, Linus Torvalds wrote:
> Hmm. I just realized when I saw Sasha's autoselect patches flying by
> that the floppy ioctl fixes didn't get marked for stable, but they
> probably should be.
> 
> There's four commits:
> 
>   da99466ac243 floppy: fix out-of-bounds read in copy_buffer
>   9b04609b7840 floppy: fix invalid pointer dereference in drive_name
>   5635f897ed83 floppy: fix out-of-bounds read in next_valid_format
>   f3554aeb9912 floppy: fix div-by-zero in setup_format_params
> 
> that look like stable material - even if I sincerely hope that the
> floppy driver isn't critical for anybody.
> 
> I leave it to the stable people to decide if they care. I don't think
> the hardware matters any more, but I could imagine that people still
> use it for some virtual images and have a floppy device inside a VM
> for that reason.

Thanks for the reminder, I'll queue these up for the next round of
stable releases after the next ones go out in a day or so.

greg k-h

  reply	other threads:[~2019-07-19 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  4:29 Floppy ioctl range clamping fixes Linus Torvalds
2019-07-19 17:07 ` Greg KH [this message]
2019-07-22  0:38   ` Sasha Levin

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=20190719170718.GA32664@kroah.com \
    --to=greg@kroah.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).