public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: lkp@intel.com, kbuild-all@01.org, viro@zeniv.linux.org.uk,
	torvalds@linux-foundation.org, socketpair@gmail.com,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] pipe: limit the per-user amount of pages allocated in pipes
Date: Mon, 18 Jan 2016 16:29:46 +0100	[thread overview]
Message-ID: <20160118152946.GA24428@1wt.eu> (raw)
In-Reply-To: <201601190012.FDB13008.HJOFSFOLMtVFQO@I-love.SAKURA.ne.jp>

On Tue, Jan 19, 2016 at 12:12:44AM +0900, Tetsuo Handa wrote:
> Willy Tarreau wrote:
> > On Mon, Jan 18, 2016 at 08:22:10PM +0800, kbuild test robot wrote:
> > > Hi Willy,
> > > 
> > > [auto build test WARNING on linus/master]
> > > [also build test WARNING on next-20160118]
> > > [cannot apply to tip/sched/core v4.4]
> > > [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
> > 
> > Well, I don't understand how to read the output here, I'm sorry. Since this
> > patch modifies the user_struct, it has a dependency on the following patch
> > just merged into Linus tree :
> > 
> >    712f4aa ("unix: properly account for FDs passed over unix sockets")
> > 
> > That's probably why you have the "cannot apply" error above.
> 
> The output says that description for newly added field is missing.
> I think adding some description like
> 
>   *      @fasync_readers: reader side fasync
>   *      @fasync_writers: writer side fasync
>   *      @bufs: the circular array of pipe buffers
> + *      @user: the user who created this pipe
>   **/
>  struct pipe_inode_info {
>          struct mutex mutex;
> 
> will fix.

Ah you're right, I've checked the other warnings that were reported around
and that's it. I wasn't aware that a bot was reading comments, I thought it
was a build warning.

I'm going to resend a v4.

Thanks,
Willy

  reply	other threads:[~2016-01-18 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 11:06 [PATCH v3] pipe: limit the per-user amount of pages allocated in pipes Willy Tarreau
2016-01-18 12:22 ` kbuild test robot
2016-01-18 12:32   ` Willy Tarreau
2016-01-18 15:12     ` Tetsuo Handa
2016-01-18 15:29       ` Willy Tarreau [this message]
2016-01-18 15:36 ` [PATCH v4] " Willy Tarreau
2016-01-20  0:07   ` Linus Torvalds
2016-01-20  0:11     ` Al Viro

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=20160118152946.GA24428@1wt.eu \
    --to=w@1wt.eu \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=socketpair@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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