From: Benjamin Poirier <bpoirier@nvidia.com>
To: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH v2 makedumpfile 0/3] Add option to limit file size
Date: Fri, 30 Jul 2021 12:51:00 +0900 [thread overview]
Message-ID: <YQN3JOljzkSV7FZh@d3> (raw)
In-Reply-To: <TYYPR01MB6777627C98AFB7AB5C849B13DDEC9@TYYPR01MB6777.jpnprd01.prod.outlook.com>
On 2021-07-30 02:13 +0000, HAGIO KAZUHITO(萩尾 一仁) wrote:
> -----Original Message-----
> > See feature description in patch "Add -L option to limit output file
> > size"
> >
> > v1:
> > http://lists.infradead.org/pipermail/kexec/2021-June/022728.html
> > v2:
> > Add patches 1, 2 to support dmesg limit with different kernel
> > versions.
> >
> > Stricter parsing of -L option value.
> >
> > Instead of using RLIMIT_FSIZE, use write_bytes or SEEK_CUR to
> > enforce limit. This better integrates with the -F option for
> > stdout output.
>
> sorry for the delay, and thank you for the update and fix.
>
> Note that the v2 patchset cannot be built except for x86_64, so I moved
> the memparse() from sadump_info.c to tools.c. Otherwise, looks good.
>
> https://github.com/makedumpfile/makedumpfile/compare/9df519d...f0cfa86
>
Thank you for checking and correcting that.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2021-07-30 3:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 7:06 [PATCH v2 makedumpfile 0/3] Add option to limit file size Benjamin Poirier
2021-07-08 7:06 ` [PATCH v2 makedumpfile 1/3] Fix off by one error when checking cache_size Benjamin Poirier
2021-07-08 7:06 ` [PATCH v2 makedumpfile 2/3] Dump dmesg using write_and_check_space() Benjamin Poirier
2021-07-08 7:06 ` [PATCH v2 makedumpfile 3/3] Add -L option to limit output file size Benjamin Poirier
2021-07-30 2:13 ` [PATCH v2 makedumpfile 0/3] Add option to limit " HAGIO KAZUHITO(萩尾 一仁)
2021-07-30 3:51 ` Benjamin Poirier [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=YQN3JOljzkSV7FZh@d3 \
--to=bpoirier@nvidia.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox