public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Tulak <jtulak@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
	Eric Sandeen <sandeen@sandeen.net>
Subject: Re: xfsdump cleaning patchset
Date: Mon, 22 Oct 2018 10:43:16 -0700	[thread overview]
Message-ID: <20181022174316.GA28561@infradead.org> (raw)
In-Reply-To: <CACj3i73FyABTkX1eCDvL+ccUhD1kWowS92=PFVyGiPvi6HWGFQ@mail.gmail.com>

On Mon, Oct 22, 2018 at 07:26:17PM +0200, Jan Tulak wrote:
> Hi guys
> 
> I did some xfsdump cleaning where I focused on getting rid of all the
> memory leaks reported by Coverity. There is still a lot of things to
> do for another time: issues by Coverity that were not fixed in this
> set, sprintf -> snprintf because there is a plenty of places for
> buffer overflow, etc...
> 
> The set has about 30 patches, so I won't spam the mailing list with
> the first iteration of review and instead, I uploaded it here:
> https://github.com/jtulak/xfsdump/tree/for-review

Please send an actual patch series, github is completely unusable
for reviews..

  reply	other threads:[~2018-10-23  2:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 17:26 xfsdump cleaning patchset Jan Tulak
2018-10-22 17:43 ` Christoph Hellwig [this message]
2018-10-22 18:07   ` Eric Sandeen
2018-10-22 19:25     ` Eric Sandeen
2018-10-23  8:16       ` Jan Tulak
2018-10-23 12:10         ` Eric Sandeen
2018-10-23 13:15           ` Jan Tulak
2018-10-23 13:43             ` Eric Sandeen
2018-10-23 14:06               ` Jan Tulak
2018-10-23 14:34                 ` Eric Sandeen

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=20181022174316.GA28561@infradead.org \
    --to=hch@infradead.org \
    --cc=jtulak@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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