Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1572865
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts |
| Date | 2017-02-03 04:20 +0100 |
| Message-ID | <t6CzL-4ui-9@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <sT0LE-36Q-7@gated-at.bofh.it> <t666R-8hp-1@gated-at.bofh.it> <t6f0u-5UQ-3@gated-at.bofh.it> <t6qIh-5eS-9@gated-at.bofh.it> <t6Bkl-3rz-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 3 Feb 2017 10:57:57 +0900
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote:
ell. sure, no objections, but in this particular case it's hardly
possible
> to hit all of those problems within a reasonable time. so what I did was just
> a bunch of dirty hacks to provoke the problems. something like this
>
> extern int XXX;
>
> vprintk_emit()
> {
> spin_lock(&logbuf_lock);
>
> //
> // in various places
> //
> if (XXX == 1) {
> WARN_ON(1);
> }
>
> spin_unlock(&logbuf_lock);
> }
>
> and I set/clear that XXX from one of sysfs attrs... yeah, I know...
> but it does what I want. so I'm not really sure I want to note this
> in the change log. am I wrong?
No you are not. But just seeing this in email does help. And yeah, this
is the type of testing that I do as well on things like this. No need
to put it in the change log.
-- Steve
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Steven Rostedt <rostedt@goodmis.org> - 2017-02-01 17:40 +0100
Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-02-02 03:10 +0100
Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Steven Rostedt <rostedt@goodmis.org> - 2017-02-02 15:40 +0100
Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Petr Mladek <pmladek@suse.com> - 2017-02-02 17:20 +0100
Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2017-02-03 03:00 +0100
Re: [PATCHv7 5/8] printk: report lost messages in printk safe/nmi contexts Steven Rostedt <rostedt@goodmis.org> - 2017-02-03 04:20 +0100
csiph-web