All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>
Subject: Re: [PATCH] remove the raw driver
Date: Mon, 31 May 2021 10:21:02 +0200	[thread overview]
Message-ID: <CAK8P3a0sctUYZnRBxS+PLted8_O1mT8JisLqO4jMHQaU=Q5iNw@mail.gmail.com> (raw)
In-Reply-To: <YLSSgyznnaUPmRaT@kroah.com>

On Mon, May 31, 2021 at 9:38 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Mon, May 31, 2021 at 10:25:26AM +0300, Christoph Hellwig wrote:
> > The raw driver used to provide direct unbuffered access to block devices
> > before O_DIRECT was invented.  It has been obsolete for more than a
> > decade.
>
> What?  Really?  We can finally do this?  Yes!
>
> For some reason, I thought there was some IBM userspace tools that
> relied on this device, if not, then great!
>
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Acked-by: Arnd Bergmann <arnd@arndb.de>
Link: https://lore.kernel.org/lkml/Pine.LNX.4.64.0703180754060.6605@CPE00045a9c397f-CM001225dbafb6/

The discussion from 2007 is the last one I could find on lore that has
useful information on when and why this was not removed in the past.
The driver was scheduled from a 2005 removal in 2004, but not removed
because both Red Hat and SuSE relied on the feature in their distros.

From what I could find out, this continued to be the case in Red Hat
Enterprise Linux 6 and SUSE Linux Enterprise server 11 that were
supported between 2009 and 2020, but the following versions dropped
the support.

       Arnd

  parent reply	other threads:[~2021-05-31  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31  7:25 [PATCH] remove the raw driver Christoph Hellwig
2021-05-31  7:38 ` Greg KH
2021-05-31  7:39   ` Greg KH
2021-05-31  8:21   ` Arnd Bergmann [this message]
2021-05-31  8:24     ` Hannes Reinecke
2021-06-04 13:36       ` Greg KH

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='CAK8P3a0sctUYZnRBxS+PLted8_O1mT8JisLqO4jMHQaU=Q5iNw@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.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 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.