From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: md: dm-writeback: add __noreturn to BUG-ging function
Date: Fri, 20 Nov 2020 09:08:20 -0500 [thread overview]
Message-ID: <20201120140819.GA7359@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.2011181611470.16933@file01.intranet.prod.int.rdu2.redhat.com>
On Wed, Nov 18 2020 at 4:24pm -0500,
Mikulas Patocka <mpatocka@redhat.com> wrote:
>
>
> On Wed, 18 Nov 2020, Mike Snitzer wrote:
>
> > On Wed, Nov 18 2020 at 10:49am -0500,
> > Mike Snitzer <snitzer@redhat.com> wrote:
> >
> > > I don't think my suggestion will help.. given it'd still leave
> > > persistent_memory_claim() without a return statement.
> > >
> > > Think it worthwhile to just add a dummy 'return 0;' after the BUG().
> >
> > Decided to go with this, now staged for 5.11:
> > https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-5.11&id=a1e4865b4dda7071f3707f7e551289ead66e38b1
>
> Hi
>
> I would just use "return -EOPNOTSUPP;" and drop the "#ifdef
> DM_WRITECACHE_HAS_PMEM" that you added.
>
> That BUG/return -EOPNOTSUPP code can't happen at all - if
> DM_WRITECACHE_HAS_PMEM is not defined, WC_MODE_PMEM(wc) always returns
> false - so persistent_memory_claim and BUG() can't ever be called. And if
> it can't be called, you don't need to add a code that prints an error in
> that case.
>
> If we don't have DM_WRITECACHE_HAS_PMEM, the compiler optimizer will
> remove all the code guarded with if (WC_MODE_PMEM(wc)) as unreachable.
>
> Mikulas
Fair enough.
prev parent reply other threads:[~2020-11-20 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 22:52 [PATCH] md: dm-writeback: add __noreturn to BUG-ging function Randy Dunlap
2020-11-16 7:30 ` Christian Borntraeger
2020-11-16 23:00 ` Randy Dunlap
2020-11-17 16:31 ` Mike Snitzer
2020-11-18 15:49 ` Mike Snitzer
2020-11-18 16:07 ` Mike Snitzer
2020-11-18 16:35 ` Christian Borntraeger
2020-11-18 16:38 ` Randy Dunlap
2020-11-18 21:24 ` Mikulas Patocka
2020-11-20 14:08 ` Mike Snitzer [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=20201120140819.GA7359@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=dm-devel@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=rdunlap@infradead.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