LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org> To: "Joel Fernandes (Google)" <joel@joelfernandes.org> Cc: LKML <linux-kernel@vger.kernel.org>, kernel-team@android.com, Anton Vorontsov <anton@enomsg.org>, Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com> Subject: Re: [RFC 2/6] pstore: remove type argument from ramoops_get_next_prz Date: Fri, 26 Oct 2018 20:05:40 +0100 [thread overview] Message-ID: <CAGXu5jLLzuwmO6C8nQp3YY0KC0yBiDSJ_U6-Xk1g8T8hzhcZpQ@mail.gmail.com> (raw) In-Reply-To: <20181026180042.52199-2-joel@joelfernandes.org> On Fri, Oct 26, 2018 at 7:00 PM, Joel Fernandes (Google) <joel@joelfernandes.org> wrote: > Since we store the type of the prz when we initialize it, we no longer > need to pass it again in ramoops_get_next_prz since we can just use that > to setup the pstore record. So lets remove it from the argument list. > > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org> Yes yes. I like where this is going. :) -Kees > --- > fs/pstore/ram.c | 20 +++++++------------- > 1 file changed, 7 insertions(+), 13 deletions(-) > > diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c > index c7cd858adce7..cbfdf4b8e89d 100644 > --- a/fs/pstore/ram.c > +++ b/fs/pstore/ram.c > @@ -125,9 +125,7 @@ static int ramoops_pstore_open(struct pstore_info *psi) > > static struct persistent_ram_zone * > ramoops_get_next_prz(struct persistent_ram_zone *przs[], uint *c, uint max, > - u64 *id, > - enum pstore_type_id *typep, enum pstore_type_id type, > - bool update) > + u64 *id, enum pstore_type_id *typep, bool update) > { > struct persistent_ram_zone *prz; > int i = (*c)++; > @@ -147,7 +145,7 @@ ramoops_get_next_prz(struct persistent_ram_zone *przs[], uint *c, uint max, > if (!persistent_ram_old_size(prz)) > return NULL; > > - *typep = type; > + *typep = prz->type; > *id = i; > > return prz; > @@ -257,8 +255,7 @@ static ssize_t ramoops_pstore_read(struct pstore_record *record) > while (cxt->dump_read_cnt < cxt->max_dump_cnt && !prz) { > prz = ramoops_get_next_prz(cxt->dprzs, &cxt->dump_read_cnt, > cxt->max_dump_cnt, &record->id, > - &record->type, > - PSTORE_TYPE_DMESG, 1); > + &record->type, 1); > if (!prz_ok(prz)) > continue; > header_length = ramoops_read_kmsg_hdr(persistent_ram_old(prz), > @@ -274,20 +271,18 @@ static ssize_t ramoops_pstore_read(struct pstore_record *record) > > if (!prz_ok(prz)) > prz = ramoops_get_next_prz(&cxt->cprz, &cxt->console_read_cnt, > - 1, &record->id, &record->type, > - PSTORE_TYPE_CONSOLE, 0); > + 1, &record->id, &record->type, 0); > > if (!prz_ok(prz)) > prz = ramoops_get_next_prz(&cxt->mprz, &cxt->pmsg_read_cnt, > - 1, &record->id, &record->type, > - PSTORE_TYPE_PMSG, 0); > + 1, &record->id, &record->type, 0); > > /* ftrace is last since it may want to dynamically allocate memory. */ > if (!prz_ok(prz)) { > if (!(cxt->flags & RAMOOPS_FLAG_FTRACE_PER_CPU)) { > prz = ramoops_get_next_prz(cxt->fprzs, > &cxt->ftrace_read_cnt, 1, &record->id, > - &record->type, PSTORE_TYPE_FTRACE, 0); > + &record->type, 0); > } else { > /* > * Build a new dummy record which combines all the > @@ -306,8 +301,7 @@ static ssize_t ramoops_pstore_read(struct pstore_record *record) > &cxt->ftrace_read_cnt, > cxt->max_ftrace_cnt, > &record->id, > - &record->type, > - PSTORE_TYPE_FTRACE, 0); > + &record->type, 0); > > if (!prz_ok(prz_next)) > continue; > -- > 2.19.1.568.g152ad8e336-goog > -- Kees Cook
next prev parent reply other threads:[~2018-10-26 19:05 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-26 18:00 [RFC 1/6] pstore: map pstore types to names Joel Fernandes (Google) 2018-10-26 18:00 ` [RFC 2/6] pstore: remove type argument from ramoops_get_next_prz Joel Fernandes (Google) 2018-10-26 19:05 ` Kees Cook [this message] 2018-10-26 18:00 ` [RFC 3/6] pstore: remove max " Joel Fernandes (Google) 2018-10-26 19:22 ` Joel Fernandes 2018-10-26 19:27 ` Kees Cook 2018-10-26 19:40 ` Joel Fernandes 2018-10-26 19:22 ` Kees Cook 2018-10-26 18:00 ` [RFC 4/6] pstore: further reduce ramoops_get_next_prz arguments by passing record Joel Fernandes (Google) 2018-10-26 19:32 ` Kees Cook 2018-10-26 19:36 ` Joel Fernandes 2018-10-26 18:00 ` [RFC 5/6] pstore: donot treat empty buffers as valid Joel Fernandes (Google) 2018-10-26 19:39 ` Kees Cook 2018-10-26 20:22 ` Joel Fernandes 2018-10-26 18:00 ` [RFC 6/6] Revert "pstore/ram_core: Do not reset restored zone's position and size" Joel Fernandes (Google) 2018-10-26 18:16 ` Kees Cook 2018-10-26 18:22 ` Joel Fernandes 2018-10-26 19:42 ` Kees Cook 2018-10-26 20:09 ` Joel Fernandes 2018-10-26 19:04 ` [RFC 1/6] pstore: map pstore types to names Kees Cook 2018-10-26 20:35 ` Joel Fernandes 2018-10-26 20:41 ` Kees Cook
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=CAGXu5jLLzuwmO6C8nQp3YY0KC0yBiDSJ_U6-Xk1g8T8hzhcZpQ@mail.gmail.com \ --to=keescook@chromium.org \ --cc=anton@enomsg.org \ --cc=ccross@android.com \ --cc=joel@joelfernandes.org \ --cc=kernel-team@android.com \ --cc=linux-kernel@vger.kernel.org \ --cc=tony.luck@intel.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: linkBe 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; as well as URLs for NNTP newsgroup(s).