All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: using dev_coredumpv
Date: Mon, 7 Sep 2015 18:35:58 +0200	[thread overview]
Message-ID: <55EDBCEE.1040008@broadcom.com> (raw)
In-Reply-To: <1441619646.1940.2.camel@sipsolutions.net>

On 09/07/2015 11:54 AM, Johannes Berg wrote:
> On Mon, 2015-09-07 at 11:47 +0200, Arend van Spriel wrote:
>> Hi Johannes,
>>
>> I am looking at devcoredump subsystem and I was wondering about the
>> lifetime of the devcd folder. With dev_coredumpm() the description says:
>> "If a previous one hasn't been read yet, the new coredump is
>> discarded.". I am wondering what "read" means here. For testing I call
>> dev_coredumpv() every second, but when I hexdump the data file it does
>> not create a new devcd folder. That only occurs after 5 minutes. Is that
>> expected?
>
> I suppose "read" should say "discarded by userspace", but I always
> assumed userspace would read the file and then discard the coredump by
> writing (anything iirc) to the file.

Thanks. Went back to devcoredump.c and reading the code found that 
devcd_data_write schedules devcd_del work without any condition. Sorry 
for being lazy.

Gr. AvS

> IOW - yes, this is expected, you should write to the data file which
> makes it (and the folder) disappear and allows creating a new one.
>
> johannes
>


      reply	other threads:[~2015-09-07 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07  9:47 using dev_coredumpv Arend van Spriel
2015-09-07  9:54 ` Johannes Berg
2015-09-07 16:35   ` Arend van Spriel [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=55EDBCEE.1040008@broadcom.com \
    --to=arend@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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 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.