From: Dan Aloni <da-x@gmx.net>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@osdl.org>
Subject: Re: [TRIVIAL] avoid Oops in net/core/dev.c
Date: Sat, 28 Jun 2003 23:07:43 +0300 [thread overview]
Message-ID: <20030628200743.GA19658@callisto.yi.org> (raw)
In-Reply-To: <20030628194102.GA2384@kroah.com>
On Sat, Jun 28, 2003 at 12:41:02PM -0700, Greg KH wrote:
> On Sat, Jun 28, 2003 at 11:38:10AM +0300, Dan Aloni wrote:
> >
> > BTW2, the attempt to rename the device here doesn't affect
> > sysfs. Patrick, we need a class_device_* interface that does
> > this.
>
> That's a good idea (I'm the person to blame for the class_device code,
> not Pat.) Care to send a patch?
I have no patch, but I thought of either using lookup_one_len()
and then d_move() to create a new dentry or to rip out some
code out of vfs_rename_dir(). Anyway, I'm no VFS expert, so
no patch any time soon.
--
Dan Aloni
da-x@gmx.net
prev parent reply other threads:[~2003-06-28 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 8:38 [TRIVIAL] avoid Oops in net/core/dev.c Dan Aloni
2003-06-28 19:41 ` Greg KH
2003-06-28 20:07 ` Dan Aloni [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=20030628200743.GA19658@callisto.yi.org \
--to=da-x@gmx.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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 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).