public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
	Petr Mladek <pmladek@suse.com>, Jiri Kosina <jikos@kernel.org>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] livepatch: Cleanup message handling in klp_try_switch_task()
Date: Thu, 25 Apr 2019 09:02:01 +0530	[thread overview]
Message-ID: <20190425033201.GC24416@JAVRIS.in.ibm.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1904242045360.30239@pobox.suse.cz>

On Wed, Apr 24, 2019 at 08:48:58PM +0200, Miroslav Benes wrote:
> On Wed, 24 Apr 2019, Josh Poimboeuf wrote:
> 
[...]
> > >  	ret = save_stack_trace_tsk_reliable(task, &trace);
> > > -	WARN_ON_ONCE(ret == -ENOSYS);
> > > +	if (ret == -ENOSYS) {
> > > +		if (!enosys_warned) {
> > > +			printk_deferred(KERN_WARNING "%s: save_stack_trace_tsk_reliable() not supported on this architecture.\n",
> > > +					__func__);
> > > +			enosys_warned = 1;
> > > +		}
> > > +		return ret;
> > > +	}
> > 
> > We already have a similar printk in patch 1, so is this warning really
> > needed?
> 
> I don't think so. pr_warn() in klp_enable_patch() should be enough in my 
> opinion.
> 
> However,
> 
> if (ret == -ENOSYS)
> 	return ret;
> 
> would be justified, wouldn't it?
> 

Probably an one line comment on why we return, will be helpful.

-- 
Kamalesh


      reply	other threads:[~2019-04-25  3:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  8:55 [PATCH 0/3] livepatch/stacktrace: Clean up of reliable stacktrace errors Petr Mladek
2019-04-24  8:55 ` [PATCH 1/3] livepatch: Convert error about unsupported reliable stacktrace into a warning Petr Mladek
2019-04-24 15:51   ` Josh Poimboeuf
2019-04-24 18:31   ` Miroslav Benes
2019-04-25  3:18   ` Kamalesh Babulal
2019-04-29 14:44   ` Petr Mladek
2019-04-24  8:55 ` [PATCH 2/3] stacktrace: Remove superfluous WARN_ONCE() from save_stack_trace_tsk_reliable() Petr Mladek
2019-04-24  9:07   ` Petr Mladek
2019-04-24 15:50   ` Josh Poimboeuf
2019-04-24 15:51   ` Josh Poimboeuf
2019-04-24 18:35   ` Miroslav Benes
2019-04-25  3:22   ` Kamalesh Babulal
2019-04-24  8:55 ` [PATCH 3/3] livepatch: Cleanup message handling in klp_try_switch_task() Petr Mladek
2019-04-24 10:41   ` Jiri Kosina
2019-04-24 12:49     ` Petr Mladek
2019-04-24 15:55   ` Josh Poimboeuf
2019-04-24 18:48     ` Miroslav Benes
2019-04-25  3:32       ` Kamalesh Babulal [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=20190425033201.GC24416@JAVRIS.in.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=pmladek@suse.com \
    /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