All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] fbarray: make all fbarrays hidden files
Date: Mon, 23 Apr 2018 21:56:01 +0200	[thread overview]
Message-ID: <1528313.VrkqK0vgdz@xps> (raw)
In-Reply-To: <f1e2dfb7-278c-8310-c198-1a2c17f7dfdc@intel.com>

23/04/2018 15:47, Burakov, Anatoly:
> On 23-Apr-18 1:48 PM, Bruce Richardson wrote:
> > On Mon, Apr 23, 2018 at 12:14:13PM +0100, Anatoly Burakov wrote:
> >> fbarray stores its data in a shared file, which is not hidden.
> >> This leads to polluting user's HOME directory with visible
> >> files when running DPDK as non-root. Change fbarray to always
> >> create hidden files by default.
> >>
> >> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> >> ---
> >>
> >> Notes:
> >>      Is /tmp always user-accessible? Maybe not use home
> >>      directory at all?
> >>
> > Good change.
> > 
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied, thanks


> > A further improvement would to put the files as not-hidden but inside a
> > hidden subdirectory e.g. ".dpdk"
> 
> Good suggestions, I'll work on this.

There are other places where we create file.
Please try to move all in the same place.

      reply	other threads:[~2018-04-23 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 11:14 [PATCH] fbarray: make all fbarrays hidden files Anatoly Burakov
2018-04-23 12:48 ` Bruce Richardson
2018-04-23 13:47   ` Burakov, Anatoly
2018-04-23 19:56     ` Thomas Monjalon [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=1528313.VrkqK0vgdz@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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.