Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1722591

Re: boot failure with 4.13.0-rc6 due to ATA errors

From Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Newsgroups linux.kernel
Subject Re: boot failure with 4.13.0-rc6 due to ATA errors
Date 2017-08-29 18:10 +0200
Message-ID <ujRfs-4Ns-27@gated-at.bofh.it> (permalink)
References (4 earlier) <ujO7U-2G2-7@gated-at.bofh.it> <ujQjn-4d0-5@gated-at.bofh.it> <ujQMq-4mN-37@gated-at.bofh.it> <ujR5M-4uX-17@gated-at.bofh.it> <ujR5M-4uX-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, 29 Aug 2017, Tejun Heo wrote:
> On Tue, Aug 29, 2017 at 12:51:02PM -0300, Henrique de Moraes Holschuh wrote:
> > > > > ATA-8 and later mirrors the TRUSTED COMPUTING SUPPORTED bit in word 48 of
> > > > > the IDENTIFY DEVICE data.  Check this before issuing a READ LOG PAGE
> > > > > command to avoid issues with buggy devices.  The only downside is that
> > > > > we can't support Security Send / Receive for a device with an older
> > > > > revision due to the conflicting use of this field in earlier
> > > > > specifications.
> > > 
> > > Christoph, I'm gonna revert the horkage patch and apply this one.  If
> > > you can think of a better way to do this, please let me know.
> > 
> > The one thing that comes to mind would be an additional patch to allow
> > people with ATA-7 to bypass the identify device data, and rely just on
> > the read log page check, based on a kernel command line parameter.
> > 
> > If we get enough sucessful reports to make it worth it, an whitelist
> > could be added...
> 
> If the ones we miss are the ones based on old revisions, does it
> matter?  If we have to, we can just whitelist those devices and I

Well, only if the opal functionality would actually be worth something
on those old revisions I guess.  It is certainly possible that it would
be better off disabled.

> don't expect there to be many.

Indeed, but we will not get much on the way of people testing this if we
don't give them a kernel parameter ;-)

-- 
  Henrique Holschuh

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

boot failure with 4.13.0-rc6 due to ATA errors David Ahern <dsahern@gmail.com> - 2017-08-28 20:50 +0200
  Re: boot failure with 4.13.0-rc6 due to ATA errors Tejun Heo <tj@kernel.org> - 2017-08-28 22:00 +0200
    Re: boot failure with 4.13.0-rc6 due to ATA errors David Ahern <dsahern@gmail.com> - 2017-08-28 22:30 +0200
      Re: boot failure with 4.13.0-rc6 due to ATA errors Tejun Heo <tj@kernel.org> - 2017-08-28 23:30 +0200
        Re: boot failure with 4.13.0-rc6 due to ATA errors Christoph Hellwig <hch@lst.de> - 2017-08-29 14:50 +0200
          Re: boot failure with 4.13.0-rc6 due to ATA errors Tejun Heo <tj@kernel.org> - 2017-08-29 16:30 +0200
          Re: boot failure with 4.13.0-rc6 due to ATA errors David Ahern <dsahern@gmail.com> - 2017-08-29 17:10 +0200
            Re: boot failure with 4.13.0-rc6 due to ATA errors Tejun Heo <tj@kernel.org> - 2017-08-29 17:40 +0200
              Re: boot failure with 4.13.0-rc6 due to ATA errors Tejun Heo <tj@kernel.org> - 2017-08-29 18:00 +0200
                Re: boot failure with 4.13.0-rc6 due to ATA errors Henrique de Moraes Holschuh <hmh@hmh.eng.br> - 2017-08-29 18:10 +0200
              Re: boot failure with 4.13.0-rc6 due to ATA errors Henrique de Moraes Holschuh <hmh@hmh.eng.br> - 2017-08-29 18:00 +0200
          Re: boot failure with 4.13.0-rc6 due to ATA errors Tejun Heo <tj@kernel.org> - 2017-08-29 17:40 +0200

csiph-web