All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Chris Wright <chris@wirex.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	David Howells <dhowells@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix net/rxrpc/proc.c
Date: Mon, 12 May 2003 19:00:36 -0700	[thread overview]
Message-ID: <20030512190036.B20068@figure1.int.wirex.com> (raw)
In-Reply-To: <1052790558.9169.2.camel@rth.ninka.net>; from davem@redhat.com on Mon, May 12, 2003 at 06:49:18PM -0700

* David S. Miller (davem@redhat.com) wrote:
> On Mon, 2003-05-12 at 17:38, Chris Wright wrote:
> > A recent change in 2.5.69-bk from Yoshfuji broke compilation of rxrpc
> > code.  It erroneously adds an owner field to the rxrpc_proc_peers_ops
> > seq_operations.  Fix below.
> 
> Why is it "erroneous"?  Just add the proper linux/module.h include
> to net/rxrpc/proc.c instead of spewing baseless claims.

Sorry, if I'm missing the obvious, but looking at my current bk tree I
see this:

include/linux/seq_file.h

struct seq_operations {
	void * (*start) (struct seq_file *m, loff_t *pos);
	void (*stop) (struct seq_file *m, void *v);
	void * (*next) (struct seq_file *m, void *v, loff_t *pos);
	int (*show) (struct seq_file *m, void *v);
};

It looks to me like there is a simple mistake of seq_operations !=
file_operations when adding .owner = THIS_MODULE to the file_operations.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2003-05-13  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  0:38 [PATCH] fix net/rxrpc/proc.c Chris Wright
2003-05-13  1:49 ` David S. Miller
2003-05-13  2:00   ` Chris Wright [this message]
2003-05-13  2:26     ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-13  3:05       ` Chris Wright
2003-05-13  3:07         ` David S. Miller
2003-05-13  3:13         ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-13  9:21         ` David Howells
2003-05-13  9:25           ` David Howells

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=20030512190036.B20068@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=davem@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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.