All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: o-takashi@sakamocchi.jp
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA: firewire-lib: schedule work again when MIDI substream has rest of MIDI messages
Date: Thu, 15 Oct 2015 10:04:18 +0300	[thread overview]
Message-ID: <20151015070418.GA7076@mwanda> (raw)

Hello Takashi Sakamoto,

This is a semi-automatic email about new static checker warnings.

The patch e8a40d9bcb23: "ALSA: firewire-lib: schedule work again when 
MIDI substream has rest of MIDI messages" from Oct 9, 2015, leads to 
the following Smatch complaint:

sound/firewire/lib.c:88 async_midi_port_callback()
	 error: we previously assumed 'substream' could be null (see line 77)

sound/firewire/lib.c
    76	
    77		if (rcode == RCODE_COMPLETE && substream != NULL)
                                               ^^^^^^^^^^^^^^^^^
Existing code assumes substream can be NULL.

    78			snd_rawmidi_transmit_ack(substream, port->consume_bytes);
    79		else if (!rcode_is_permanent_error(rcode))
    80			/* To start next transaction immediately for recovery. */
    81			port->next_ktime = ktime_set(0, 0);
    82		else
    83			/* Don't continue processing. */
    84			port->error = true;
    85	
    86		port->idling = true;
    87	
    88		if (!snd_rawmidi_transmit_empty(substream))
                                                ^^^^^^^^^
Patch adds an unchecked dereference (inside the function call).

    89			schedule_work(&port->work);
    90	}

regards,
dan carpenter

             reply	other threads:[~2015-10-15  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15  7:04 Dan Carpenter [this message]
2015-10-15  8:18 ` ALSA: firewire-lib: schedule work again when MIDI substream has rest of MIDI messages Takashi Sakamoto

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=20151015070418.GA7076@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=o-takashi@sakamocchi.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.