linux-kernel - Re: [RESEND PATCH] nvdimm: fix some compilation warnings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7ba8164b60be4e41707559ed6623f9462c942735.camel@intel.com>
Date:   Thu, 16 May 2019 00:25:18 +0000
From:   "Verma, Vishal L" <vishal.l.verma@...el.com>
To:     "Williams, Dan J" <dan.j.williams@...el.com>,
        "cai@....pw" <cai@....pw>
CC:     "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Jiang, Dave" <dave.jiang@...el.com>,
        "Busch, Keith" <keith.busch@...el.com>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "Weiny, Ira" <ira.weiny@...el.com>
Subject: Re: [RESEND PATCH] nvdimm: fix some compilation warnings

On Wed, 2019-05-15 at 16:25 -0700, Dan Williams wrote:
> 
> > diff --git a/drivers/nvdimm/btt.c b/drivers/nvdimm/btt.c
> > index 4671776f5623..9f02a99cfac0 100644
> > --- a/drivers/nvdimm/btt.c
> > +++ b/drivers/nvdimm/btt.c
> > @@ -1269,11 +1269,9 @@ static int btt_read_pg(struct btt *btt, struct bio_integrity_payload *bip,
> > 
> >                 ret = btt_data_read(arena, page, off, postmap, cur_len);
> >                 if (ret) {
> > -                       int rc;
> > -
> >                         /* Media error - set the e_flag */
> > -                       rc = btt_map_write(arena, premap, postmap, 0, 1,
> > -                               NVDIMM_IO_ATOMIC);
> > +                       btt_map_write(arena, premap, postmap, 0, 1,
> > +                                     NVDIMM_IO_ATOMIC);
> >                         goto out_rtt;
> 
> This doesn't look correct to me, shouldn't we at least be logging that
> the bad-block failed to be persistently tracked?

Yes logging it sounds good to me. Qian, can you include this in your
respin or shall I send a fix for it separately (since we were always
ignoring the failure here regardless of this patch)?