linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: linux-next: proc tree build failure
Date: Fri, 23 Jan 2009 22:26:07 +0300	[thread overview]
Message-ID: <20090123192607.GF8491@localhost> (raw)
In-Reply-To: <20090123184147.GA3340@x200.localdomain>

[Alexey Dobriyan - Fri, Jan 23, 2009 at 09:48:37PM +0300]
...
| > Hi Stephen,
| > 
| > thanks for catching this. Until I miss something --
| > s_fs_info for /proc is struct pid_namespace* right?
| > So maybe_get_net will convert it to net*, which is
| > not right I guess. On the other hand -- and PDE, and
| > PDE_NET is defined in proc_fs.h regardless if CONIG_PROC_FS
| > is turned on/off. Confused...
| > 
| > (to be fair -- this maybe_get_net(PDE_NET(PDE(inode))) is
| >  taken from proc_net.c:get_proc_net, but to eliminate #ifdef
| >  I reimplemented it, which is not good too -- maybe I've been
| >  to put get_proc_net into some header, Eric?)
| 
| PDE_NET here is bogus. you should use seq_open_net/seq_release_net.
| See how other code does this, plenty of examples.
| 

The question is not in examples, I saw that code.
There is some problem with seq_open_net/seq_release_net --
I don't need additional private data for sequential files,
all I need is just a pointer (ie -- seq_file.private) which
is already allocated for seq_file structure itself. So
Alexey, why should I use seq_open_net then and ask for
additional memory which I don't need? (side note:
actually get_net/put_net is really needed here indeed).

		- Cyrill -

  reply	other threads:[~2009-01-23 19:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  6:15 linux-next: proc tree build failure Stephen Rothwell
2009-01-23  7:09 ` Cyrill Gorcunov
2009-01-23 18:48   ` Alexey Dobriyan
2009-01-23 19:26     ` Cyrill Gorcunov [this message]
2009-01-23 19:41       ` Cyrill Gorcunov
2009-01-23 20:26         ` Cyrill Gorcunov
2009-01-24 22:00   ` [PATCH] pppol2tp: stop using proc internals Alexey Dobriyan
2009-01-25  8:47     ` Cyrill Gorcunov
2009-01-27  5:10       ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-03-30  6:43 linux-next: proc tree build failure Stephen Rothwell
2008-11-24  7:15 Stephen Rothwell
2008-11-28  8:05 ` Alexey Dobriyan
2008-11-28  9:00   ` David Miller
2008-11-28 10:25     ` David Miller
2008-11-20  6:24 Stephen Rothwell
2008-11-20  8:43 ` Eric W. Biederman
2008-11-10  5:29 Stephen Rothwell
2008-11-10  5:53 ` Alexey Dobriyan
2008-11-10  7:36   ` Ingo Molnar
2008-10-21  7:21 Stephen Rothwell

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=20090123192607.GF8491@localhost \
    --to=gorcunov@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).